I have been looking at the Ant Rpm task. It looks like it is simply a means to execute the rpmbuild command on an existing build root. That doesn't seem too hard to adapt if plexus already has a means to run external commands while capturing the output.
The Maven 1 rpm plugin is not much more code than that. It assumes that you have a compressed tar file with the files you want packaged into the RPM. It has no way to introduce installation scripts into the package and no way to mark files to have special consideration (permissions, ownership, etc). I went back and found the Maven projects where I had playing in Maven 1 with building RPMs. It turns out that I had completely re-written the plugin so that it was rather flexible in how things were packaged. With that flexibility, of course, came a lot of complications in how things were configured. I'll have to do some looking in plexus-archiver to see about supporting RPMs. From what I have looked at so far, it seems that the current formats are done by writing the file directly, adding items to it as directed by the mojo. In the case of an RPM file, we would need to build a directory tree (need an initialization method to initialize the tree), copy files as directed by the mojo, then call the external command to build the RPM file (need a termination method to do this). Does this sound like something that is doable? -----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 30, 2005 22:57 To: Maven Developers List Subject: Re: Lifecycle Plugin Development Assistance Request There is another option here - should we add support for RPM to plexus-archiver, using the code from Ant? Note, the future plans for this are to introduce plexus-archiver to jakarta-commons (there is already a compress module there based on the same code from Ant). - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
