You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2017/05/30 08:39:22 UTC
[jira] [Closed] (OAK-6035) Mark AbstractLoginModule and
Authentication as provider types
[ https://issues.apache.org/jira/browse/OAK-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davide Giannella closed OAK-6035.
---------------------------------
Bulk close for 1.7.0
> Mark AbstractLoginModule and Authentication as provider types
> -------------------------------------------------------------
>
> Key: OAK-6035
> URL: https://issues.apache.org/jira/browse/OAK-6035
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: security
> Affects Versions: 1.7.0, 1.8
> Reporter: Robert Munteanu
> Assignee: Alex Parvulescu
> Labels: modularization
> Fix For: 1.7.0, 1.8
>
> Attachments: 0001-OAK-6035-Mark-AbstractLoginModule-and-Authentication.patch
>
>
> With OAK-5903 the {{AbstractLoginModule}} and {{Authentication}} interfaces received new methods and the exported package version was bumped from 1.1.0 to 2..0.0. This is unfortunately a breaking change for anyone importing the {{org.apache.jackrabbit.oak.spi.security.authentication}}, including Sling's oak-server module.
> To me these classes do not look as they are usually implemented by clients, but part of an SPI implemented mostly by oak-core, e.g. they are 'provider types' in OSGi vocabulary.
> I've marked them with the {{@ProviderType}} annotation which allows the exported package version to only be increased to 1.2.0 and allows consumer to reference those packages without changing import ranges across all Oak version.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)