[
https://issues.apache.org/jira/browse/SLING-8735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935948#comment-16935948
]
Robert Munteanu commented on SLING-8735:
----------------------------------------
[~olli] - consider the following scenario:
- bundle at version 1.2.7-SNAPSHOT
- make a change that requires bumping minor version
- bnd fails the build until you move to 1.3.0-SNAPSHOT
We have the even/odd versioning policy, so this needs to be 1.3.1-SNAPSHOT . So
we release at 1.3.2 and 1.3.0 is gone. Which is not bad if it happens once, but
as a policy it does not make sense.
Alternatively, we skip baselining, which I did, but then this is problematic
since we miss exported package versions check.
> Ignore bundle version baselining messages
> -----------------------------------------
>
> Key: SLING-8735
> URL: https://issues.apache.org/jira/browse/SLING-8735
> Project: Sling
> Issue Type: Improvement
> Components: General
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: Bundle Parent 36
>
>
> More recent versions of bnd also verify the bundle version (in addition to
> the package version) during baselining as recommended in
> https://www.osgi.org/developer/white-papers/semantic-versioning/bundles-and-fragments/.
> 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
> https://github.com/bndtools/bnd/issues/3446#issuecomment-534098094.
> Further discussion can be found in
> https://lists.apache.org/thread.html/cde09fb1f483b74791e0fdaeff4fad1aee3006232062e38dcbf33e31@%3Cdev.sling.apache.org%3E
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
