[ 
https://issues.apache.org/jira/browse/OAK-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16048836#comment-16048836
 ] 

Chetan Mehrotra commented on OAK-6346:
--------------------------------------

bq. Do you consider this an interim solution or would this be permanent. What's 
the process to update this new base version as we approach a 1.8.0 release with 
a 1.8 branch if this is considered permanent?

IMHO we can have it as permanent. For every major release done the base version 
can be changed to refer to that release

bq. If we go with the patch, can you please add a comment to the oak-core 
artifactId configuration in oak-api pom.xml?

That was done because due to m18n packages present in oak-api need to be 
compared against packages present in oak-core for 1.6.0 version. Similar 
changes would need to be done for other modules which have been carved out of 
oak-core. Once we have an agreement over the approach I can look into changes 
required in other modules

> Set baseline plugin comparison version to 1.6.0
> -----------------------------------------------
>
>                 Key: OAK-6346
>                 URL: https://issues.apache.org/jira/browse/OAK-6346
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: parent
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.8
>
>         Attachments: OAK-6346-v1.patch
>
>
> The purpose of baseline plugin is to ensure that any change in api get 
> reflected in exported version of the package. Currently the baseline plugin 
> compares against the immediate previous version. 
> This causes issue with unstable branches where new features are being 
> implemented and which evolve over few minor release on the trunk. In such 
> cases its possible that a new method expose in 1.7.1 gets removed later in 
> 1.7.2 (as happened in OAK-6337).
> It would be better to configure baseline plugin to check against releases 
> from stable branch so that we can ensure that package versions are properly 
> aligned against stable versions



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to