[
http://jira.codehaus.org/browse/MRPM-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208356#action_208356
]
Rob ten Hove commented on MRPM-47:
----------------------------------
This is exactly what we need. We're dealing with a lot of artefacts and a lot
of dependencies. All these artefacts need to be installed on RedHat system, so
RPM is a good choice. Since Maven has all the dependency information, mapping
it on RPM Requires seems like a logical step. We don't want to include all
dependencies in each RPM!
> 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
