[
http://jira.codehaus.org/browse/MRPM-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190570#action_190570
]
Scott Jones commented on MRPM-47:
---------------------------------
You probably would want a switch in the module to handle the versions
differently.
We include just the package name in dependencies for RPMs.
Leave the ability to declare the depencies like you have it today.
Add the ability to inherit the depencies from the project dependencies with
version numbers or without. This is the fun part :)
> 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
