[
https://issues.apache.org/jira/browse/FELIX-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483973
]
Alin Dreghiciu commented on FELIX-262:
--------------------------------------
That's the same approach used for sping-osgi but with the osgi plugin.
I agree that can be an work around or even a better approach if we would like
to keep maven-bundle-plugin at a minimum but to me looks verbose.
Not very sure about the following but you will have to add the dependencies
anyhow to your pow because otherwise those dependencies will not be pulled into
the local repo for the dependency plugin. And then again you will have to mark
them as provided if you do not want them as transient dependency (back to the
original problem)
> 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.
