[
https://issues.apache.org/jira/browse/SLING-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499575#comment-14499575
]
Stefan Seifert commented on SLING-3944:
---------------------------------------
same here (with AEM and sling models, the problems appears sporadically) - most
time a restart of the instance helps resolving the issue, but sometimes event
this does not help depending on the naming/loading order of the bundles. i was
able to get partially around the problem with setting different run levels for
the different bundles, but this is only a hack. it seems to be an osgi problem
in the current felix implementation. i've on my todo list to create a test
setup to reproduce the problem and if it is reproducible standalone create a
felix ticket for it.
> 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)
