[
https://issues.apache.org/jira/browse/FELIX-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515368
]
Craig L. Ching commented on FELIX-308:
--------------------------------------
I think this is probably a new JIRA issue, but Richard Hall asked me to comment
here. On the users list, I found out that if I include a bundle as a
dependency in another project, the dependencies that went into the bundle also
become dependencies in the current project. The resolution to this was to use
<exclusions>, e.g.:
what we are doing at the moment to avoid your problems is to add
exclude statements to our dependencies i.e.,
<dependency>
<groupId>${groupId}</groupId>
<artifactId>org.apache.felix.framework</artifactId>
<exclusions>
<exclusion>
<groupId>${pom.groupId}</groupId>
<artifactId>org.osgi.core</artifactId>
</exclusion>
</exclusions>
</dependency>
So my question is, will this JIRA cover this? In other words, I don't want to
maintain my dependencies in two places. If an artifact is included in the
bundle, that artifact should not be considered a dependency in the dependent
project.
> Add support for embedding dependency JAR files to bundle plugin
> ---------------------------------------------------------------
>
> Key: FELIX-308
> URL: https://issues.apache.org/jira/browse/FELIX-308
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
> Reporter: Richard S. Hall
>
> The following is a proposal for how to support embedding dependency JAR files
> in the bundle plugin. The general approach is a slightly modified version of
> a proposal by Peter Kriens. The idea is to add a mechanism to deal with
> embedding JARs that is very similar to how the old maven plugin worked, but
> doing it in a slightly more generic way than the old plugin by adding the
> following instruction:
> embed-dependency ::= clause ( ',' clause ) *
> clause ::= MATCH ( ';' attr '=' MATCH )
> attr ::= 'groupId' | 'artifactId' | 'version' | 'scope'
> MATCH ::= <globbed regular expressions>
> This instruction would be used to match the specified Maven dependencies for
> embedding. Any matching dependency would have its JAR file embedded onto the
> resulting bundle JAR file and it would be appended to the Bundle-ClassPath
> header after ".".
> This would allow people to easily achieve the same behavior as the old plugin
> by simply doing:
> <embed-dependency>*;scope=compile,*;scope=runtime</embed-dependency>
> Thus, this instruction would automatically embed any maven dependencies that
> were of scope "compile" or "runtime" and append them to the bundle class path.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
