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

David Bosschaert updated SLING-3493:
------------------------------------

    Attachment: SLING-3493.diff

The attached SLING-3493.diff patch fixes these issues.

The dependency error in the commons/compiler is caused by an import indirectly 
referenced from an eclipse component: org.osgi.service.prefs. This import is 
not needed so I removed it.

The import range on org.osgi.framework in scripting/java is wrong, which is 
caused by a transitive dependency of the o.a.s.commons.compiler component. I 
have excluded that in Maven so that the correct version of this package is 
picked up from the org.osgi.core module.

> Javashell demo doesn't work
> ---------------------------
>
>                 Key: SLING-3493
>                 URL: https://issues.apache.org/jira/browse/SLING-3493
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons, Samples
>            Reporter: David Bosschaert
>         Attachments: SLING-3493.diff
>
>
> The JavaShell demo doesn't work because its dependencies have issues with 
> their metadata.
> The JavaShell demo has dependencies on the org.apache.sling.commons.compiler 
> and org.apache.sling.scripting.java bundles.
> Both these bundles don't resolve.
> The org.apache.sling.commons.compiler bundle has:
>   org.osgi.service.prefs,version=[1.1,2) -- Cannot be resolved
> The org.apache.sling.scripting.java bundle has:
>   org.osgi.framework,version=[1.7,2) -- Cannot be resolved



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to