[
http://jira.codehaus.org/browse/MRPM-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208404#action_208404
]
Brett Okken commented on MRPM-47:
---------------------------------
"The result is a large .tar.gz which contains all RPM's." This sounds like a
completely different artifact (with its own pom).
And even that case, how do you pick (and configure the assembly plugin) as to
which transitive dependencies to include (rpms, jars, wars, zips, .tar.gzs,
etc.)? Remember that rpm projects almost certainly have actual build time
dependencies (something has to go in the rpm).
I admit I may be slow, but I am missing the use case. Why would my rpm project
my-tomcat-assembly have a build time dependency (which is what <dependencies>
section is for) on my-http-server.rpm? What from my-http-server.rpm do I need
to /build/ my-tomcat-assembly.rpm?
I cannot think of a single use case to have data duplicated in <dependencies>
and rpm.<configuration>.<requires>.
What am I missing?
> 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
