Manos Batsis wrote: > > > On a similar issue, I just noticed that my custom plugin works fine in > the site lifecycle but breaks when calling a goal directly as M2 thinks > it's a maven plugin; my understanding is M2 uses the wrong groupId when > trying to check the repo for it (should be > gr.abiss.mvn.plugins:maven-jstools-plugin instead of > org.apache.maven.plugins:maven-jstools-plugin).
This is a different issue. You have to declare a pluginGroup in your settings.xml to instruct Maven to look for additional groupIds. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
