[
https://issues.apache.org/jira/browse/SLING-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137150#comment-14137150
]
Justin Edelson commented on SLING-3944:
---------------------------------------
It is fine to use a dedicated bundle, but that is up to the deployer. There's
no reason to force the use of a dedicated bundle in this case.
This issue doesn't have anything to do with Jackrabbit or Sling Models. It is
only about the fact that the Scripting Java 2.0.10 bundle has (due to some
change in the build envrionment) the wrong export version. Forcing more
deployment complexity is *not* the right answer to that problem.
> org.apache.sling.scripting.java bundle exports javax.inject package in wrong
> version
> ------------------------------------------------------------------------------------
>
> Key: SLING-3944
> URL: https://issues.apache.org/jira/browse/SLING-3944
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting Java 2.0.10
> Reporter: Markus Haack
> Assignee: Oliver Lietz
> Priority: Critical
> Fix For: Scripting Java 2.0.12
>
>
> The org.apache.sling.scripting.java bundle exports the package javax.inject
> in the version of the bundle, which is wrong and should be fixed.
> This can lead to bundle version problems for other bundles which depend on
> javax.inject in version "[1.0,2)" - the correct version (like Jersey Web
> Services libraries).
> Either export javax.inject with version 0.0.0 or even better with the correct
> version 1.0.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
