-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everybody,
> Please add a JIRA in the at jira.codehaus.org for the mojo project in > the component plugin-submission. > Please check they enforce the mojo guidelines (defined in the mojo web > site mojo.codehaus.org) I am not sure if you all got me right: I wrote a simple but flexible plugin that allows to create packages for solaris. (But yep, I would submitt it to Mojo (sandbox first of all) and be available for maintainance) In Mojo I found such plugins for RPM and DEB that already exist. All of these plugins have the same goal: create a deployment package of the outcome of a maven module. But also all of them do it completely different and have a different philosophy. I would love to have a discussion with the various makers of these plugins and/or all that are interested and find a common way to solve this issue with maven. Creating totally different animals for the same major task seems odd to me. I use maven in private for my open-source projects as well as for the business. This use-case is more an enterprise need, but I have much experience in deplyoment strategies (already solved this issue several times both with core ANT and with Maven) and would provide my knowledge. But before writing another RPM plugin, I would like to bring these things together. FYI: The Mojo RPM Plugin was written by Bob Allison. The Mojo DEB Plugin was written by Trygve Laugstol. I do not know if these guys just dumped the plugins to MOJO or if they are active community members. Anyways everybody interested in this toppic is welcome to get into discussion. Here are some openers to think about: - -Should the package-format be the packaging declared in the POM or should it more likely be the name of the plugins goal? - -Should there be a Parent-POM that all packaging modules should derive from? This could override various defaults of the Super-POM that does not apply in this case and especially could establish senseful defaults for the packaging module. - -Should we create an abstract Mojo that all deployment package plugins should derive from? This could contain some common logic. > > Regards, > > Raphaël Best regards Jörg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGFWDbmPuec2Dcv/8RAmEgAJoCM1+HQsGRW73knqsKkEX2kqh1qQCdHGJU qdk7u2mwIEaWsBokU2VfVnw= =WPAO -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
