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 annotation, 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: http://maven.40175.n5.nabble.com/Call-a-custom-plugin-from-another-project-tp5758214p5758242.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org