When you run Maven, you usually specify a lifecycle phase such as
install or package or deploy.     Maven will then execute every
lifecycle phase sequentially until it reaches the specified phase.
If you want a full list of lifecycle phases take a look at the Maven
docs here:  http://tr.im/shS4   - I would suggest attaching your build
script to either verify or initialize.

If you have a build.xml file and you want it to run before anything
interesting happens, hook it up to the verify phase...

<project>
  [...]
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-antrun-plugin</artifactId>
        <executions>
          <execution>
            <phase>verify</phase>
            <configuration>
              <tasks>
                  <ant antfile="build.xml" target="whatever"/>
              </tasks>
            </configuration>
            <goals>
              <goal>run</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>
  [...]
</project>


On Tue, Jul 14, 2009 at 8:10 AM, REMIJAN, MICHAEL J
[AG/1000]<[email protected]> wrote:
> I have an ANT script which I want to make sure runs first before any
> maven goal is run.  How would I go about configuring this?
>
> ---------------------------------------------------------------------------------------------------------
> This e-mail message may contain privileged and/or confidential information, 
> and is intended to be received only by persons entitled to receive such 
> information. If you have received this e-mail in error, please notify the 
> sender immediately. Please delete it and all attachments from any servers, 
> hard drives or any other media. Other use of this e-mail by you is strictly 
> prohibited.
>
>
> All e-mails and attachments sent and received are subject to monitoring, 
> reading and archival by Monsanto, including its subsidiaries. The recipient 
> of this e-mail is solely responsible for checking for the presence of 
> "Viruses" or other "Malware". Monsanto, along with its subsidiaries, accepts 
> no liability for any damage caused by any such code transmitted by or 
> accompanying this e-mail or any attachment.
> ---------------------------------------------------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> 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]

Reply via email to