This is what is happening with Maven2. It's being built around a lightweight container (called Plexus). It is indeed the goal that plugins are developed in Java or in other languages. -- Vincent MassolI don't really understand why he wants to use Plexus were there is already Spring, Pico and HiveMind.
And that just what Jason Carreira said (in a very polite way ;-) )
If the Maven community wants to be taken seriously you guys really need to stop making bone-headed decisions like this. Plexus? Who the hell is using that? Just because it's someone's pet project is no reason to base an already questionable project on it. When you're trying to sway public opinion (much of which has been negative toward Maven so far) you have to go out of your way to be mainstream and make it easy for people to use. This is why Venture Capitalists won't let startup companies base their business off of a dependency on another startup company. Maybe Plexus offers something that Spring doesn't (I doubt it), but is it really worth the risk of Plexus dying or just of people like me and Hani pointing and laughing at the silly decisions?Jason is one of those people.
-- Jason Carreira
3 comments:
Hi Francisoud,
Just a note: _I_ don't want anything. I'm not part of the team who made the decision to use plexus or any other tool :-)
But honestly I don't care. I say, let the people who do the development chose what they want.
As a m2 user you won't see any of plexus at all.
> I'm not part of the team who made the decision to use plexus or any other tool
I didn't know that. Sorry for the misinterpretation...
> let the people who do the development chose what they want.
Since people involve in open source projects do it for free, I totaly agree that they should have fun with those projects...
But when evaluating tools such as Spring, Pico, HiveMind... I which people stop creating new projects from scratch and try to get involve in one that already exist to make it better instead of just creating an other one...
It seems some developpers start creating new sourceforge project instead of just looking for something that already exist and (almost) do what they want!
> As a m2 user you won't see any of plexus at all.
As a user I won't care too :)
Saying there is a negative groundswell around maven is like saying there is a negative groundswell around apple or a negative groundswell around microsoft.
It's a no-op. It means nothing. maven is successful already. (Theres plenty of evidence for that.) Just because a group doesn't like it doesn't mean they'll influence anyone else. This kind of opinion exists everywhere in the software world.
Now, start tackling the the technical, point by point and you'll have something. But remember, this is open source, your points will probably be inaccurate by the time google indexes them (due to them being answered).
Food for thought: plexus is a generic IoC container. those are not that hard to write. dozens of them exist. what really matters is the components. how many components exist in the other IoC frameworks (container + components) that address the needs of the software development process?
as vincent said, plexus is just an internal library, not visible to the user of m2 at all. in fact, even as a developer of plugins for m2 you'll barely even be aware of it.
Post a Comment