This sounds similar to my requirement of splitting the package phase into pre-package and package. Pre-package would assemble the exploded archive, whereas package would perform the archiving itself. This would allow other mojos to contribute to the archive assembly phase as you require.
See http://www.mail-archive.com/dev@maven.apache.org/msg62286.html Mark On 04/12/06, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
That's interesting. Could you please fill something in JIRA with your use case and a sample? Thanks, Stéphane On 12/1/06, Simone Gianni <[EMAIL PROTECTED]> wrote: > > Hi all, > I've developed a couple of plugin (one performs XML patches, the other > builds a certain site structure). They both should work on the WAR > directory structure, but before the WAR file is currently built. > > Apart from my specific needs, it could be quite common to need to > perform some tasks (with an antrun for example) on the WAR directory > structure before zipping it in the WAR file. > > Is there a way to hook these plugins (or any plugins) in between of the > WAR plugin? In case, could it be a good idea to split the WAR plugin in > two different goals so that it's possible to prepare the WAR directory > structure and zip it in two different phases? > > Another option could be to use the WAR plugin to produce the directory > structure (copying all the dependencies jars in place, doing war overlay > etc..) and then use the assembly plugin (or antrun with a jar task :) ) > to produce the final WAR file. Is this possible? > > Thanks, > Simone > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
