[
https://issues.apache.org/jira/browse/OAK-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376702#comment-14376702
]
Michael Dürig commented on OAK-2006:
------------------------------------
The baseline feature depends on the Maven artefact numbering scheme for
determining the base version to compare against. This order needs to be
consistent with the order of the exported package version contained in the
artefacts. For the 1.1.x release train this is not the case as we kept
resetting back to 1.1-SNAPSHOT after each unstable release. Due to this we need
to configure (and update) the base version in the poms. To keep this manageable
I propose to set the base version to 1.0. In essence this means we only do
semantic versions for stable releases and skip it for unstable releases for
now. I think this is the right thing to do because frankly, it is what we did
with the 1.1.x releases in the first place. Once we proceed with 1.3.x releases
we need to rethink this and decide whether we also want to do semantic
versioning for the 1.3.x unstable minor releases and if so, we need to
respectively number the snapshot versions (i.e. 1.3.x-SNAPSHOT).
> Verify the maven baseline output and fix the warnings
> -----------------------------------------------------
>
> Key: OAK-2006
> URL: https://issues.apache.org/jira/browse/OAK-2006
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Alex Parvulescu
> Assignee: Michael Dürig
> Labels: build
> Fix For: 1.1.8
>
> Attachments: baseline-oak-core.patch
>
>
> Currently the maven baseline plugin only logs the package version mismatches,
> it doesn't fail the build. It would be beneficial to start looking at the
> output and possibly fix some of the warnings (increase the OSGi package
> versions).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
