I would prefer not be core change dependent. Some folks are still using 2.x . And 'classloader scanning' at runtime level will have IHMO a performance cost ! So I would prefer plugin metadata generation (the trick will be having the mix of doclet and annotations : perso I'm not sure it's a good idea to have both ? )
-- Olivier Send from a VT100 phone console Le 27 avr. 2012 18:26, "Robert Scholte" <[email protected]> a écrit : > +100 > > I've had a talk about this with Simone this month. > He'd done some investigation already. > I think there are two separate steps to be taken. > 1. Generate the plugin.xml based on both annotations and doclets > 2. Extend Maven Core to understand Mojo Annotations as well > > The first one would already be a huge improvement for all mojo-devs. > > -Robert > > Op Fri, 27 Apr 2012 16:36:57 +0200 schreef Olivier Lamy <[email protected] > >: > > Hi, >> I'd like to work on 1.5 Annotations for Mojos. >> Hervé started documentation here: >> https://cwiki.apache.org/**confluence/display/MAVEN/Java+** >> 5+Annotations+for+Plugins<https://cwiki.apache.org/confluence/display/MAVEN/Java+5+Annotations+for+Plugins> >> >> The Stephen's idea for named without Mojo prefix looks fine (at least >> for me). But I would prefer to not implement (yet) the other idea with >> synthetic bridging classes. >> >> I can start the job next week (probably in a branch). >> >> Comments ? >> >> Thanks, >> > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > [email protected].**org<[email protected]> > For additional commands, e-mail: [email protected] > >
