[
https://issues.apache.org/jira/browse/FELIX-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484012
]
Carlos Sanchez commented on FELIX-262:
--------------------------------------
i don't see the scope as the solution, is a workaround, it's not designed to do
that
there are two cases here:
- bundle = original library + OSGi manifest
I think this is the best solution, if you do it from the original library pom,
you just need the bundle:manifest goal, if you do it from outside somehow you
should deploy the dependencies section from the pom in the original library
instead of the current one.
- bundle = several libraries
this will require http://jira.codehaus.org/browse/MNG-2316 to be implement
first to list all the dependencies provided by the bundle
> Scope of wrapped dependencies from felix commons
> ------------------------------------------------
>
> Key: FELIX-262
> URL: https://issues.apache.org/jira/browse/FELIX-262
> Project: Felix
> Issue Type: Improvement
> Components: Felix Commons
> Reporter: Alin Dreghiciu
>
> Most/Some (I did not check) wrapper bundles have the dependency to the
> wrapped library expressed without any <scope>. This means that it will be the
> default = COMPILE. Nothing wrong till here but by the moment that I will
> express a dependency on the wrapper = those from the felix commons, due to
> transitivity, will also pull the original wrapped library, fact that is not
> required since is already in the bundle.
> So, all the pom's must be changed to add a <scope>PROVIDED</scope> to all
> dependencies.
> If you need help let me know.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
