maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From alesky <>
Subject Re: Call a custom plugin from another project
Date Tue, 04 Jun 2013 17:16:25 GMT
ok Stephen thanks 

specifying an execution to the plugin it works

but i would like to injects an execution in the packaging for the specified
plugin project 
in the way that i can use the plugin in this way, and don't have to force
the user to specific the execution

but i didn't found any documentation on-line or in the reference guide
regarding this point 
or at list I'm not able to find a correct on-line document to do it

what i i found is that in the plugin annotation there is the @execute
but from my understand this annotation is complete different from what i
want to do

@execute goal="<goal>"
This will execute the given goal before execution of this one. The goal name
is specified using the prefix:goal notation.
@execute phase="<phase>"
This will fork an alternate build lifecycle up to the specified phase before
continuing to execute the current one. If no lifecycle is specified, Maven
will use the lifecycle of the current build.
@execute lifecycle="<lifecycle>" phase="<phase>"
This will execute the given alternate lifecycle. A custom lifecycle can be
defined in META-INF/maven/lifecycles.xml.

View this message in context:
Sent from the Maven - Users mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message