which version Guice supports qualifier annotations
@Qualifier
@Target({ TYPE, METHOD, FIELD })
@Retention(RUNTIME)
?
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> From: [email protected]
> Subject: Re: Developing MOJOs using JSR-330
> Date: Sun, 14 Nov 2010 07:54:14 -0500
> To: [email protected]
>
>
> On Nov 12, 2010, at 7:44 PM, Christopher Hunt wrote:
>
> > Hi Jason,
> >
> > Thanks for the reply.
> >
> > In effect then, Plexus lives; at least in terms of developing Mojos. I
> > suppose I thought that the idea was to ultimately de-couple from Plexus.
> >
>
> Plexus the implementation does not live. But with Guice, as Stuart has
> answered, mimics Plexus as there is no feasible way we could just stop
> supporting Plexus. Every plugin, component and configuration would break.
>
> > In my perfect world, I'd prefer to leverage JSR-330 knowledge and not have
> > to do with Plexus at all when writing Mojos. There's enough out there to
> > learn without another container, and I think that having to learn Plexus
> > impacts on who writes Mojos.
>
> In my perfect world Maven, Nexus, Hudson and M2E plugins will be written
> against JSR-330 so we're on the same page there. We made the changes to the
> underlying systems with your perspective in mind. No one really wants to
> learn N APIs when one will do. But we just can't stop supporting Plexus cold
> turkey, that's just an unworkable situation.
>
> Sonatype has been testing the JSR-330 approach in Nexus and Hudson for over
> six months, and we are just introducing it into M2E now. But Maven has the
> more users then any of those systems so it's the one we're moving slowest on.
>
> >
> > May be in a year or so when M3 is widely adopted, this will be less of a
> > concern.
> >
> > Kind regards,
> > Christopher
> >
> > On 10/11/2010, at 7:45 PM, Jason van Zyl wrote:
> >
> >> On Nov 10, 2010, at 12:46 AM, Christopher Hunt wrote:
> >>
> >>> Thanks Oliver.
> >>>
> >>> I think that it'll be quite a while before people write MOJOs just for
> >>> Maven 3. From my own perspective having just written two new MOJOs, I'd
> >>> like to be able to write for the future but recognise the present. It'd
> >>> be great to use @inject in my code now and then use the MOJO with Maven
> >>> 2. Not possible?
> >>>
> >>
> >> Not impossible, but a huge amount of work to get to work in Maven2 and I'm
> >> not aware of anyone doing any work in this area to make JSR-330 work in
> >> Maven 2. But it's definitely within the realm of possibility in Maven 3.
> >>
> >
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> A party which is not afraid of letting culture,
> business, and welfare go to ruin completely can
> be omnipotent for a while.
>
> -- Jakob Burckhardt
>
>
>
