> On 20 Sep 2019, at 12:36, Konrad Windszus <[email protected]> wrote: > > 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 >
The OSGi installer does care about versions and it seems that a version with a qualifier is greater than one without. So 1.2.7-SNAPSHOT or 1.2.7.1568987500 are greater than 1.2.7. The Felix Web Console doesn’t seem to care at all about bundle versions. I was able to replace a 1.2.7 with a 1.2.6 by POSTing to /system/console/bundles. I guess that as long as we support the OSGi installer we cannot get rid of the odd/even release policy. Thanks, Radu
