[ https://issues.apache.org/jira/browse/SLING-11531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Norman resolved SLING-11531. --------------------------------- Resolution: Fixed Merged PR #16 at: [{{eaddcb6}}|https://github.com/apache/sling-org-apache-sling-jcr-jackrabbit-usermanager/commit/eaddcb642695cbdce11f14a37b44ced84ee66199] > add RequestParameter factory to Builders > ---------------------------------------- > > Key: SLING-11531 > URL: https://issues.apache.org/jira/browse/SLING-11531 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman > Priority: Major > Fix For: JCR Jackrabbit User Manager 2.2.26, API 2.26.2 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > As discussed at SLING-11525 > Expected: > Add a newRequestParameter factory method to the > [Builders|https://github.com/apache/sling-org-apache-sling-api/blob/master/src/main/java/org/apache/sling/api/request/builder/Builders.java] > class from sling.api so the duplicated RequestParameterImpl class can be > removed from the org.apache.sling.jcr.jackrabbit.usermanager bundle and use > the new factory instead. > The motivation for this is to remove the tight coupling of the > org.apache.sling.api.request package between the sling.api and usemanager > bundles that is caused by implementing The RequestParameter interface that > has been annotated as a ProviderType. > Without this change, every time that the exported version number of the > o.a.sling.api.request package changes, the usermanager must bump the version > of the dependency and release a new usermanger version to satisfy the narrow > version range that was being imported for that package. -- This message was sent by Atlassian Jira (v8.20.10#820010)