jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-6346) Set baseline plugin comparison version to 1.6.0
Date Mon, 03 Jul 2017 12:08:00 GMT

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

Marcel Reutegger commented on OAK-6346:

I'm in favour of applying the patch with minor changes, like adding a note to the configuration
in oak-api/pom.xml on why it is needed. It may also be good to update our [release documentation|http://jackrabbit.apache.org/jcr/creating-releases.html]
and introduce a step when a new branch is created. That would be the time when trunk needs
to bump the comparison version, right?

> 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
> 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

View raw message