[jira] [Commented] (SLING-11525) Update dependency for sling.api v2.26.0 compatibility
[
https://issues.apache.org/jira/browse/SLING-11525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17578572#comment-17578572
]
Eric Norman commented on SLING-11525:
-
[~cziegeler] Ok, I've added SLING-11531 to track that work to be done in the
next sling.api release.
I'll leave this issue open for a quick fix to ensure there is at least one
version that is compatible with sling.api v2.26.0
> Update dependency for sling.api v2.26.0 compatibility
> -
>
> Key: SLING-11525
> URL: https://issues.apache.org/jira/browse/SLING-11525
> Project: Sling
> Issue Type: Improvement
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: JCR Jackrabbit User Manager 2.2.24
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Update dependency for compatibility with sling.api v2.26.0
> Resolves this error:
> {code:java}
> [ERROR] [bundle-packages]
> org.apache.sling:org.apache.sling.jcr.jackrabbit.usermanager:2.2.22: Bundle
> is importing package org.apache.sling.api.request;version=[2.6,2.7) with
> start order 20 but no bundle is exporting these for that start order in the
> required version range.{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SLING-11525) Update dependency for sling.api v2.26.0 compatibility
[
https://issues.apache.org/jira/browse/SLING-11525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17578255#comment-17578255
]
Carsten Ziegeler commented on SLING-11525:
--
[~enorman] Yes, adding a new method to Builders sounds like a sensible solution
> Update dependency for sling.api v2.26.0 compatibility
> -
>
> Key: SLING-11525
> URL: https://issues.apache.org/jira/browse/SLING-11525
> Project: Sling
> Issue Type: Improvement
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: JCR Jackrabbit User Manager 2.2.24
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Update dependency for compatibility with sling.api v2.26.0
> Resolves this error:
> {code:java}
> [ERROR] [bundle-packages]
> org.apache.sling:org.apache.sling.jcr.jackrabbit.usermanager:2.2.22: Bundle
> is importing package org.apache.sling.api.request;version=[2.6,2.7) with
> start order 20 but no bundle is exporting these for that start order in the
> required version range.{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SLING-11525) Update dependency for sling.api v2.26.0 compatibility
[
https://issues.apache.org/jira/browse/SLING-11525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17578083#comment-17578083
]
Eric Norman commented on SLING-11525:
-
[~cziegeler] I don't think that the local RequestParameterImpl is the only
reason for the narrow version range. I believe bnd will calculate that narrow
range for any reference to package that contains a ProviderType, so the other
references to the RequestParameter interface would cause the narrow version
range as well even if there was no impl of the interface.
Regarding the local impl of RequestParameter, perhaps a better long term
approach would be to 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 here and use the factory instead. Any objections to that?
> Update dependency for sling.api v2.26.0 compatibility
> -
>
> Key: SLING-11525
> URL: https://issues.apache.org/jira/browse/SLING-11525
> Project: Sling
> Issue Type: Improvement
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: JCR Jackrabbit User Manager 2.2.24
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Update dependency for compatibility with sling.api v2.26.0
> Resolves this error:
> {code:java}
> [ERROR] [bundle-packages]
> org.apache.sling:org.apache.sling.jcr.jackrabbit.usermanager:2.2.22: Bundle
> is importing package org.apache.sling.api.request;version=[2.6,2.7) with
> start order 20 but no bundle is exporting these for that start order in the
> required version range.{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SLING-11525) Update dependency for sling.api v2.26.0 compatibility
[
https://issues.apache.org/jira/browse/SLING-11525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1752#comment-1752
]
Carsten Ziegeler commented on SLING-11525:
--
[~enorman] What is causing this narrow version import, seems to be the
usermanager is implementing a ProviderType interface which it should not do
> Update dependency for sling.api v2.26.0 compatibility
> -
>
> Key: SLING-11525
> URL: https://issues.apache.org/jira/browse/SLING-11525
> Project: Sling
> Issue Type: Improvement
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: JCR Jackrabbit User Manager 2.2.24
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Update dependency for compatibility with sling.api v2.26.0
> Resolves this error:
> {code:java}
> [ERROR] [bundle-packages]
> org.apache.sling:org.apache.sling.jcr.jackrabbit.usermanager:2.2.22: Bundle
> is importing package org.apache.sling.api.request;version=[2.6,2.7) with
> start order 20 but no bundle is exporting these for that start order in the
> required version range.{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
