You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Joel Richard (JIRA)" <ji...@apache.org> on 2015/05/06 12:44:00 UTC

[jira] [Updated] (SLING-3944) org.apache.sling.scripting.java bundle exports javax.inject package in wrong version

     [ https://issues.apache.org/jira/browse/SLING-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joel Richard updated SLING-3944:
--------------------------------
    Attachment: Screen Shot 2015-05-06 at 12.36.05.png

[~olli], the exported version is now 0, but it seems like the imported version has been set to [0.0, 1) because of this (see attached screenshot). Won't that cause further problems?

> 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
>
>         Attachments: Screen Shot 2015-05-06 at 12.36.05.png
>
>
> 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)