Thank you for the answer. I'm using this specific ant task to deploy an axis webservice ( with a program called AdminClient). I can only deploy it after my container ( in this case jetty:run ) has started.. So which phase would be relevant?
Wayne Fay wrote: > >> <execution> >> <id>Ant: deleting >> EDepotServiceBindingImpl.java</id> >> <phase>generate-sources</phase> > ... >> <execution> >> <id>Ant: Deploying service with axis-admin</id> >> <phase>pre-integration-test</phase> > ... >> As I understand, I should be able to execute my ant tasks, embedded in >> the >> above executions, with 'mvn ant:run'... But the message <echo >> message="Running axis-admin" /> is not shown in the output.. Seems lilke >> the >> tasks are not run. > > Since you bound both executions of the plugin to various phases of > your build's lifecycle, Maven will automatically execute the plugin > with those configuration values at the proper time of the lifecycle > during your build -- you do not (and should not) need to type "mvn > ant:run" -- instead just type "mvn package" or whatever lifecycle you > wish to execute. Read more here: > http://maven.apache.org/plugins/maven-antrun-plugin/ > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/maven%2C-ant%2C-antrun%3Arun-tp23720986p23737664.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
