[
http://jira.codehaus.org/browse/MRPM-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208361#action_208361
]
Brett Okken commented on MRPM-47:
---------------------------------
The dependency information must be in the pom. The question is should it be in
the <dependencies> section or in the <configuration> section of the rpm plugin.
The <dependencies> section indicates artifacts required to build the current
artifact. They are not used to indicate other assemblies that are present at
runtime. (The provided scope is kind of an exception to this. But in a java
project, for example, a provided dependency marks a dependency that is needed
either directly or transitively to compile.)
Much like maven, rpm only requires direct dependencies to be listed. There is
no need to list transitive dependencies. So I am not quite sure I see what the
benefit is of using the <dependencies> section rather than the <configuration>
section. How do you envision this working and what is the advantage?
> Inherit RPM dependencies from POM dependencies
> ----------------------------------------------
>
> Key: MRPM-47
> URL: http://jira.codehaus.org/browse/MRPM-47
> Project: Mojo RPM Plugin
> Issue Type: New Feature
> Components: rpm
> Reporter: Josh McFarlane
> Assignee: Brett Okken
>
> It'd be nice if there were some way to automatically pull generate RPM
> Requires based on the dependencies in the POM. Right now the user has to
> maintain two separate dependency lists (one for RPM, and one for Maven). If
> there were some way to reduce the amount of duplication, it'd go a long way
> towards integrating RPM more seamlessly into Maven.
> A few solutions to this approach might be:
> 1. Add any dependencies marked as provided as RPM Requires: <artifactId>
> 2. For any dependencies marked as provided, parse the dependency's pom and
> determine if it uses the RPM plugin and what the RPM name is.
> 3. Provide a way for users to disable / exclude this RPM auto-requirement
> resolution.
--
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
