-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Mark Hobson wrote: | 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. In the current setup, a small convenience API could help with using Ant tasks programmatically, which means simply setting up a mojo with parameters that you feed into the programmatic construction and configuration of the task...then you feed that task into the convenience API to execute it. I've developed that convenience API for a client, but have to make sure it's okay before I release it for public consumption. But this works well for simple Ant API calls. For more complex Ant-based processes, it would be nicer to have an adaptor that would essentially wrap an Ant script fragment as a mojo, complete with parameters and all...then the mojo would setup the Project property substitutions for those parameters, and delegate execution to the scriptlet, possibly either calling a target within a plugin-wide script resource, or else calling a mojo-specific script resource. This is what I'm currently planning, but it's going to be awhile before I can get it done. John | | Mark | | --------------------------------------------------------------------- | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDKDz4K3h2CZwO/4URAgWIAJoDWsXO8ol7n00N0Jude0mwXXZp2ACgiXeZ 1qiBj6sZkgv0DnnRJx8oI8g= =hN2V -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
