[
http://jira.codehaus.org/browse/MRPM-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227843#action_227843
]
Brett Okken commented on MRPM-78:
---------------------------------
Could your <dependencies> section exclude the transitive dependencies? For
example:
{noformat}
<dependencies>
<dependency>
<groupId>com.example</groupId>
<artifactId>otherapp</artifactId>
<version>1.2</version>
<exclusions>
<exclusion>
...
</exclusion>
...
</exclusion>
</dependency>
...
{noformat}
This (combined with dependency management) is how transitive dependencies are
typically resolved/managed for assemblies.
Another option would be to use the
[maven-dependency-plugin|http://maven.apache.org/plugins/maven-dependency-plugin]
to copy the specific jar somewhere in the target directory, then just include
the jar from there into your rpm.
> Option to exclude transitive dependencies of an excluded artifact
> -----------------------------------------------------------------
>
> Key: MRPM-78
> URL: http://jira.codehaus.org/browse/MRPM-78
> Project: Mojo RPM Plugin
> Issue Type: Improvement
> Components: rpm
> Affects Versions: 2.0.1
> Reporter: Robert Munteanu
> Assignee: Brett Okken
>
> For the moment it is not possible to filter out a dependency and all its
> transitive dependencies. This is useful when I try to 'combine' classpaths
> from two RPMs, and I want to make sure that they don't clash.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
