eg <project> ...<build> ...<plugins> ...<plugin> ...<executions> ...<execution>
On 4 June 2013 16:46, Stephen Connolly <stephen.alan.conno...@gmail.com>wrote: > plugins are not executed unless the packaging for the specified project > injects an execution OR you specify an execution for the plugin yourself > > > On 4 June 2013 16:01, alesky <alessandro.dotta...@gmail.com> wrote: > >> 1. Please use a propper mail agent that does not strip the code from you >> email >> ok i will do the next time sorry to all, i was supposing that in this way >> there was all the information to undestand my issue >> >> >> 2. Try `mvn it.spaghettisource.plugin:pojo:1.0:log` as Maven does not know >> where to look for your plugin >> >> as is wrote in my previous mail i can call correctly the plugin from >> command line: >> using >> mvn it.spaghettisource.plugin:pojo:1.0:log >> and i have registered the group in the setting so i can call it also by >> prefix >> mvn pojo:log >> >> my question is related to the fact that if i had the plugin configuration >> in >> another project >> inside the plugin section, it is not executed >> >> >> >> >> >> >> -- >> View this message in context: >> http://maven.40175.n5.nabble.com/Call-a-custom-plugin-from-another-project-tp5758214p5758217.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 >> >> >