I am working on a plugin to create a life cycle plugin to build RPMs.
As things stand right now, I have a plugin which defines the RPM life
cycle and contains mojos which just generate a warning so I know they
were called.  I have a project which uses packaging of rpm; running "m2
package" on that project runs the rpm mojos correctly.  (YEA!!)

Now comes the hard part:  making things work.  I would appreciate any
pointers, hints, suggestions, examples, etc., on how to do the
following:
-- I need a complex configuration in the POM to define the files which
need to be placed in the RPM; I have a pointer which was posted to the
developer's list on Monday on this so I think I have a reasonable start
on this
-- I would like to be able to have include and exclude lists in the
configuration, but I don't want to have to write the code to filter the
directory tree; any ideas?
-- I need to copy the files into a single directory tree for the
rpmbuild command to use to build the RPM file; is it possible to use the
plexus archiver to assemble the files into a directory and not build a
jar?
-- I was thinking of using the ant rpm task to do the actual work of
building the RPM file; any examples of having one mojo calling another
(assuming that I can access the rpm task from the antrun mojo)?

Thanks for the assistance and keep up the good work!

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to