Wayne Fay wrote: > >> 2. possibilty: >> I could simply copy all Mojo code and that of classes it's depending on >> from >> xml-maven-plugin into my plugin. This would only be a good idea if direct >> Mojo reusage is a discouraged practice in Maven plugin development. > > This, for a few reasons. > Hi Wayne,
could you please elaborate a bit on these "few reasons"? >From my point of view copied code is bad style because of its redundancy. You need to fix bugs in two several places, for example. And isn't a released, i.e. imutable version of the xml-maven-plugin as good as a separate artifact that Justin suggested which contains only the general xml processing stuff but not the Mojo code? My plugin will always be able to resolve its dependency on the xml-maven-plugin. I can't see the difference between depending on a plugin artifact and depending on a jar artifact. CU, Stefan -- View this message in context: http://old.nabble.com/Plugin-Development%3A-Best-way-to-reuse-a-Mojo-from-another-plugin--tp28137687p28143527.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
