See also [1] for some background. I am also thinking on whether we should try to separate the checks that we run:
- baselining for exported package versions on every build - baselining for the bundle version when releasing, - mvn release:prepare This would allow us to keep our strategy _and_ pick the right version number for the bundle. (This is probably not available in bnd, but maybe we could enhance it) Robert [1]: https://cwiki.apache.org/confluence/display/SLING/Thoughts+on+Release+Management On Fri, 2019-09-20 at 12:36 +0200, Konrad Windszus 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 > > > On 20. Sep 2019, at 12:32, Radu Cotescu <[email protected]> wrote: > > > > Hi Konrad, > > > > > On 20 Sep 2019, at 11:34, Konrad Windszus <[email protected]> > > > 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 > >
