[
https://issues.apache.org/jira/browse/CAMEL-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044067#comment-13044067
]
Daniel Kulp commented on CAMEL-4047:
------------------------------------
The other option MAY be to move all the javax.script stuff into the
camel-script component. It already has a bundle Activator in there that could
handle this.
That said, I'm not 100% sure if that's acceptable as there COULD be use cases
of the script things without camel-script. Thoughts?
> javax.script dependency in camel-core
> -------------------------------------
>
> Key: CAMEL-4047
> URL: https://issues.apache.org/jira/browse/CAMEL-4047
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.8.0
> Reporter: Daniel Kulp
>
> The OSGi imports for camel-core ends up with a non-optional dependency on
> javax.script due to it being used in the Activator. However, the karaf
> feature for camel-core doesn't have a dependency on
> org.apache.servicemix.specs.scripting-api-1.0 .
> One of two things should be done:
> 1) mark javax.script as optional. This MAY require some updates to the
> Activator to work when it's not available.
> 2) Update the karaf features file to add:
> {code:xml}
> <bundle
> dependency="true">mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.scripting-api-1.0/${servicemix-specs-version}</bundle>
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
