Hi! Sorry that I didn't have more time yesterday night, so I missed the most important question:
Is the @Component annotation meant to be used on the component itself (for defining the factory rule, like @ApplicationScoped) or is it used on the InjectionPoint like @Inject? Or is it like a @Qualifier (kind of a typesafe bean 'name') which gets used on both? LieGrue, strub ----- Original Message ----- > From: Brett Porter <br...@apache.org> > To: Maven Developers List <dev@maven.apache.org> > Cc: > Sent: Monday, May 21, 2012 7:22 AM > Subject: Re: Maven Plugins annotations support @Component role attribute to > Class<?> > > > On 21/05/2012, at 3:45 AM, Hervé BOUTEMY wrote: > >> here, the end-user is a plugin developer, then someone who should be able > to >> create a (Plexus) component when necessary >> >> Yes, I liked @Component too but as soon as you write a component and inject > >> somponents inside it, you discover the discrepency: the more I work on > this, >> the more I discover these little discrepencies that lost me for a long > time. >> Notice that the target is JSR330 @Inject. >> Is it too early to use @Inject? > > Agree - I didn't think @component (the Javadoc annotation) would carry over > to the plugin annotation. It should just use @Inject if that's feasible. > > - Brett > > -- > Brett Porter > br...@apache.org > http://brettporter.wordpress.com/ > http://au.linkedin.com/in/brettporter > http://twitter.com/brettporter > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
