-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Actually, what I'd really like to see in the future is the convergence of Ant APIs and Maven build process to form one ultra-rich platform for running builds and developing build plugins. If you still want to run Ant scripts, you have an optional ant-build jar or somesuch that you can include in your classpath...otherwise, Ant would become a utility project in many ways.
My 2-cents. - -john Mark Hobson wrote: | On 14/09/05, Ashley Williams <[EMAIL PROTECTED]> wrote: | |>Mark, I see what you mean about autodeducing the war file with a pure |>maven plugin. However wouldn't it be easier to write a mapping layer |>that passes the maven war location to the ant task and any other |>properties too? |> |>So instead of writing the tomcat plugin from scratch, you would |>simply wrap the ant tomcat bean with a maven ant adapter together |>with a property/xml file describing the map from maven to ant bean |>properties. | | [snip] | | This is what John was describing above with regard to an ant adapter. | I could have done this with the tomcat plugin, but after looking at | the tomcat ant tasks I decided they were too tied in with ant. The | core of the maven tomcat plugin is maven-independent | (TomcatManager.java) and would ideally be shared between the maven | plugin and the ant tasks. | | Mark | | --------------------------------------------------------------------- | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDKErwK3h2CZwO/4URAnN4AJ9ZP5CnhC7o7lxgo7YPe+fnx3HRXQCeLdsk 44/Nrx+DvOaOjOS9HKxT1gk= =fRSk -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
