[ 
http://jira.codehaus.org/browse/MRPM-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=228166#action_228166
 ] 

Brett Okken commented on MRPM-78:
---------------------------------

This actually sounds somewhat similar to the "skinny war"[1] issue with the 
maven-war-plugin. The solution suggested there is actually similar to what I am 
suggesting here.

Yet another option (though probably no less verbose), would be to mark 
dependencies expected to be provided by the "container" rpm as provided[2]. 
This will pull the dependencies into IDE, but not include them in the assembly. 
This also has the advantage of providing some documentation of what 
dependencies (including versions) expected to be provided by the container.

>> 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.
>
> So that would allow me to control the dependency using the standard 
> build/dependendencies/dependency tag, right? But I still won't have a simple 
> 'excludeTransitive' setting IIRC.

Still no simple "excludeTransitive", but you could use the <excludes> tag 
within the dependency itself, since the IDE would not matter.

[1] - http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
[2] - 
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope

> 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


Reply via email to