It seems better (in the long-run) to file a bug in JIRA and attempt to fix the issue in Maven itself than try to find a work-around. But you are certainly welcome to try this approach for now.
Wayne On 8/18/07, Teody Cue Jr. <[EMAIL PROTECTED]> wrote: > Hi Giovanni, > > You can use the maven-antrun-plugin and bind it on the phase after the > reporting plugin. Whichever phase the reporting plugin is binded. > Here's the link on maven's build lifecycle: > http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html > Check out the section "Build Lifecycle Phase Reference" for a complete > list of the phases. > > maven-antrun-plugin can be found here: > http://maven.apache.org/plugins/maven-antrun-plugin/ > However, antrun is advisable only when migrating from ant to maven. > Although it would solve your current problem. :) > > Hope this helps. > > Teody > > > > Giovanni Azua wrote: > > Hi all, > > > > I would like to run some ant at completion of the maven build process or > at > > least at completion of the reporting. The problem is that I have a > > multi-module project, and the xref reporting leaves the xref folder in > each > > submodule rather than copying it to the main project pom type. > > > > TIA, > > regards, > > Giovanni > > > > > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
