sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Sedding (Jira)" <>
Subject [jira] [Commented] (SLING-8735) Ignore bundle version baselining messages
Date Tue, 24 Sep 2019 08:34:00 GMT


Julian Sedding commented on SLING-8735:

bq. And there is nothing which prevents us beside our installer ({{1.3.0-SNAPSHOT}} > {{1.3.0}}),

Not quite. The problem is that maven has special handling for the SNAPSHOT qualifier and OSGi
does not. That leads to the situation where:

- Maven: 1.3.0-SNAPSHOT < 1.3.0
- OSGi: 1.3.0.SNAPSHOT > 1.3.0

This has proven to be a nuisance during development, because once you install your new release,
nothing gets updated and time is wasted finding out that the SNAPSHOT is still installed.

IMHO there is nothing wrong with the odd/even versioning scheme and we should stick with it.

We *could* switch it around to have odd release versions and even development versions, which
would solve the eternal issue of "loosing" the micro "0" version (i.e. 1.3.0-SNAPSHOT (even)
-> 1.3.1 (release). However, I believe that at this point this would cause more confusion
than what it's worth.



> Ignore bundle version baselining messages
> -----------------------------------------
>                 Key: SLING-8735
>                 URL:
>             Project: Sling
>          Issue Type: Improvement
>          Components: General
>            Reporter: Konrad Windszus
>            Priority: Major
>             Fix For: Bundle Parent 36
> More recent versions of bnd also verifies the bundle version (in addition to the package
versions) during baselining as recommended in
> This is currently not useful for Sling as we still follow the odd/even release version
policy for bundle versions. 
> Therefore we should disable those baselining messages as adviced in
> Further discussion can be found in

This message was sent by Atlassian Jira

View raw message