[
http://jira.codehaus.org/browse/MRPM-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208367#action_208367
]
Karl Heinz Marbaise commented on MRPM-47:
-----------------------------------------
The dependency (direct dep's no transitive) information should be part of the
pom, cause that's the Maven way...but i wouldn't close the way via
<configuration>.
I would like to see it in the pom, cause currently i'm already using
dependencies between RPM's...so the logical next step will be to put the
dependency into the RPM Requires. The result is a large .tar.gz which contains
all RPM's.
Based on that a word about the version which might go into the RPM-Requires.
Currently Maven handles versions in a particular way (best practise is to fix
the versions in pom's)....so the first step might be to put the exact version
into the requires section for the RPM..but this would result in a problem with
a larger system which comprises of e.g. hundredths of RPM's (let use assume
version 1.0). If there are dependencies defined between them it can be very
complicated to replace one RPM's e.g. with version 1.0.1 (based on a Bug
fix)...so it should be possible to define either name only or name plus version
(which goes into the required area for the 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
