Alex Deparvu commented on OAK-6539:

bq. Are there @ProviderType interfaces exposed by this package? If so, I think 
it's unsafe to change the version back.
yes I see a few of those in the package, but the tooling seems to disagree with 
you, if we trust it to enforce version bumps up why not trust it to decrease 

I guess just waiting for the code to change is also one option, but then the 
same clients you mentioned that import the bigger version will again break as 
they will not see the changes (new code but no new version export).

I'm open to alternatives, what needs to be done to get rid of the warning?

> 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