@phase process-classes
means user can skip/omit phase definition in execution.
execution element must still in the pom
-D
On 2/26/07, guilherme_silveira <[EMAIL PROTECTED]> wrote:
Hello guys,
I have seen someone had the same question as I do a few days earlier...
but
no solution (that I could understand).
I have the following mojo:
/**
* @goal translate
* @phase process-classes
*/
And would like the end-user to only write:
<plugin>
<groupId>org.vraptor</groupId>
<artifactId>vatx</artifactId>
</plugin>
So the goal translate would be called during the process-classes.
It doesnt, of course.
I think I might be missing some way to tell maven (in my plugin, and not
my
user pom.xml) to execute the "translate" goal during the process-classes
phase.
If I do <plugin>
<groupId>org.vraptor</groupId>
<artifactId>vatx</artifactId>
<executions>
<execution>
<id>annotations to xml</id>
<phase>process-classes</phase>
<goals>
<goal>translate</goal>
</goals>
</execution>
</executions>
</plugin>
It works... (of course), as I told maven (in the end-user pom) that it
should run the translate goal during such phase.
Any other option? In the plugin pom or configuration files?
Regards
Guilherme Silveira
--
View this message in context:
http://www.nabble.com/Binding-mojo-to-process-classes-phase-tf3293508s177.html#a9160898
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]