Robert Munteanu commented on OAK-6539:

This behaviour stems from the fact that the comparison baseline is 1.6.2, not 
the highest released version.

The exported version was increased in 
[r1800179|https://svn.apache.org/r1800179], so if the baseline goal would take 
into account 1.7.5, there would be an error, requiring increasing the version 
to 1.3.1, due to the annotation type changes. So it's probably OK to decrease 
the version to 1.2.0, as we (AFAIU) have the policy of managing package version 
changes only based on stable releases.

> Decrease version export for 
> org.apache.jackrabbit.oak.spi.security.authentication
> ---------------------------------------------------------------------------------
>                 Key: OAK-6539
>                 URL: https://issues.apache.org/jira/browse/OAK-6539
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, security
>            Reporter: Alex Deparvu
>            Assignee: Alex Deparvu
>            Priority: Trivial
> There's a warning when building oak-core related to the export version for 
> the org.apache.jackrabbit.oak.spi.security.authentication package:
> {noformat}
> [WARNING] org.apache.jackrabbit.oak.spi.security.authentication: Excessive 
> version increase; detected 1.3.0, suggested 1.2.0
> {noformat}
> I see no reason to not decrease the version. [~anchela], thoughts?

This message was sent by Atlassian JIRA

Reply via email to