I am not aware of any more places (e.g. OSGi Installer or Felix Web Console) where changes from SNAPSHOT to non SNAPSHOT versions would not be applied (even if the version number does not change). But maybe Carsten Ziegeler could confirm. The relevant code is IMHO https://github.com/apache/sling-org-apache-sling-installer-core/blob/33eeae619c5aae2a7a52903edbdd6a85b08e0891/src/main/java/org/apache/sling/installer/core/impl/tasks/BundleTaskCreator.java#L235 <https://github.com/apache/sling-org-apache-sling-installer-core/blob/33eeae619c5aae2a7a52903edbdd6a85b08e0891/src/main/java/org/apache/sling/installer/core/impl/tasks/BundleTaskCreator.java#L235>
Konrad > On 20. Sep 2019, at 12:32, Radu Cotescu <r...@apache.org> wrote: > > Hi Konrad, > >> On 20 Sep 2019, at 11:34, Konrad Windszus <konra...@gmx.de> wrote: >> >> a) adjust the bundle version accordingly (and rather get rid of odd/even >> release version numbers) > > Can we safely get rid of the odd/even release version numbers? IIRC we’re > using this so that a development version gets upgraded with the newest > released version in the OSGi container. > > To take Robert’s example, 1.2.7-SNAPSHOT would be a greater version than > 1.2.7. So would 1.2.7.timestamp. > > Thanks, > Radu >
