Hi Thomas, > -----Original Message----- > From: Thomas Van de Velde [mailto:[EMAIL PROTECTED] > Sent: vendredi 5 août 2005 11:14 > To: Maven Developers List > Subject: Re: [m2] getting involved? > > > > > BTW - I like plexus. Haven't noticed the project before. I had used > > avalon and had a look at pico+nano before. Plexus seems to be powerfull > > like avalon containers but less invasive (like the spring-framework). > > Maybe I'll use that in my project. Would you again decide for plexus if > > you'd choose now? > > > In what way would Spring be more invasive than Plexus? My issue with the > Plexus container is that it is completely unknown to most developers, that > there are no books and hardly any documentation on the site. I assume > there > must be good reasons for starting yet another IoC container (Can somebody > elaborate on those reasons?)
There are 2 viewpoints you need to consider: 1/ First viewpoint: As a Maven2 user or as a Maven2 plugin writer As a Maven user/plugin writer you don't have to care as it's transparent for you, even if you're writing plugins. So it's a non-issue. 2/ Second viewpoint: As a Maven core developer. In that case, you're the one developing the solution and it's your call to choose whatever technology you wish. The current Maven developers are aware of the other IOC containers but for now they have preferred to use their own. I do agree with you that one drawback is its support. That said it does also bring lots of advantages to them like the ability to quickly make changes to it to support Maven2 use cases. I believe those advantages are currently greater that the disadvantages. Conclusion: 99.9999% of all persons around Maven 2 are users and they don't need to care as it's transparent for them. -Vincent PS: This represents only my analysis of the situation. I'm not speaking for the m2 team although I believe they would agree with this :-) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
