Solved.
The issue is that I was explicitly invoking 'mvn rpm:rpm' at the root of
my project. This clearly asks each project to build an RPM which is not
the intent. Any project (module) that lacks the right configuration
would fail. So the solution is to bind the rpm goal as specified in the
docs and not explicitly invoke the rpm goal(s). IOW, "RPM on demand"
probably won't work with a multi-module EAR project.
On 07/06/2010 03:17 PM, Chris Bredesen wrote:
Hi Group,
I'm successfully creating RPMs of my WAR file using said plugin. I am
unsuccessful at creating an RPM of my EAR project. It's a multi-module
project with the EAR being one of the modules. I have tried putting the
plugin details both on the parent POM and on the EAR pom. I have tried
putting the plugin version in the parent's depmgt sectoin and the config
in the EAR pom. However, whenever I execute rpm:rpm from the parent
(actually the "root" directory in my case), I get the following:
===============================
[INFO] One or more required plugin parameters are invalid/missing for
'rpm:rpm'
[0] Inside the definition for plugin 'rpm-maven-plugin' specify the
following:
<configuration>
...
<group>VALUE</group>
</configuration>.
[1] Inside the definition for plugin 'rpm-maven-plugin' specify the
following:
<configuration>
...
<mappings>VALUE</mappings>
</configuration>.
===============================
Now the interesting part is that the POM that's being buit is the
parent, not the EAR project. So clearly it would not find any such
configuration. How do I get rpm:rpm to execute only for the EAR project
and not the parent?
Thanks,
Chris
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
