[
http://jira.codehaus.org/browse/MRPM-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=228159#action_228159
]
Brett Okken commented on MRPM-78:
---------------------------------
I am a bit confused. How can you need the dependencies to run in the IDE, but
not in the RPM?
Another option would be to separate out the rpm as its own project (instead of
a secondary artifact). This approach more closely follows maven's idea of one
project = one artifact. This also might simplify your dependency picture.
As far as I can tell, the rpm-maven-plugin matches the functionality of other
assembly type plugins (such as war, assembly, etc.) for resolving and including
dependencies (direct and transitive). I am not inclined to re-invent the wheel
here. Especially since the desired outcome can be achieved in multiple ways
(with various levels of effort).
> 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
