Stephane Nicoll wrote: > Yes, I've seen this thread as well. Sounds good to me even if we need > strong > use cases to create a new standard phase. > Basic use cases I've seen so far, applied to the WAR problem : - Cocoon team developed a plugin that deploys its blocks inside a war. This way, the user only have to specify which blocks their application depend on, and then the plugin will take them, unpack some certain files from a standard block jar structure inside some folders in the war, and do some other stuff on the web.xml and similar files. Right now this plugin has been developed as extending the AbstractWarMojo. Unfortunately this worked fine up to a certain version, but now fails with an NPE cause of what's written here http://www.mail-archive.com/dev@maven.apache.org/msg60770.html and here http://issues.apache.org/jira/browse/COCOON-1961 . - I've developed a plugin that applies XML patches to mostly every target directory structure, but if not subclassing the war mojo (and having the errors), or using other techniques (like running war exploded and then using the assembly plugin etc..), or using my patch (http://jira.codehaus.org/browse/MWAR-86 ) I have no way to see it work on a war directory structure before it gets packed. - For a project I'm doing and that I'll post on apache labs ASAP, I developed a plugin that taken a certain source folder structure creates a working cocoon application, generating sitemaps etc.. Same as above, no way to have it work to build a WAR out of it. - A friend of mine needed to run a legacy ant task on some files before packing the WAR, he wanted to use antrun but again... He ended up using war exploded and then appending to it's ant run a task to build the war.
Adding a phase is, IMHHHO, not a lightweight change. Also, adding a "pre-package" phase sounds a bit like going back to maven1 pregoals, but a way to work between the prepare and the package phase of a packaging mojo is absolutely needed. Simone --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
