[ https://issues.apache.org/jira/browse/OAK-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049020#comment-16049020 ]
Davide Giannella commented on OAK-6346: --------------------------------------- what about changes in methods signature to bring in any innovation? Overload and deprecation will eventually lead to bad code and people not adopting new code. What if/when we won't be able to avoid the major bump? Where is the line we say something like: this method does not longer exists and therefore a major bump? > 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)