On 14/09/05, Ashley Williams <[EMAIL PROTECTED]> wrote: [snip] > Well if an ant adapter was worked upon, wouldn't this mean some of > the existing plugin work is redundant, thus freeing up time? I mean > fast forward to a time where we have an ant adapter - I can't see > anyone choosing to use [maven-tomcat-plugin] over [maven-ant-adapter > + ant-tomcat-task], which is well understood and tested to death. > Correct me if there are any functional advantages in the pure maven > plugins. [snip]
Although ant tasks could theoretically be supported natively alongside mojos they will still need to be configured. Mojo's can deduce a lot about their project environment from the POM and other plugin config, and hence their configuration is minimal, whereas ant tasks typically allow every parameter to be tweaked. So even if you were to use, say, the tomcat ant task natively within maven, you'd still need to manually configure the location of the war file (depending on the war plugin config), context xml, etc. since ant tasks know nothing about the maven project layout. Simple configuration could be done via the plugin xml, but more complex ones would probably require a maven plugin wrapper. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
