« The Geronimo proposal | Main | Weblog comments: just say broken. »

Why is Maven a top level project?

I saw Maven described as being part of the "usual infrastructure" on the Geronimo site. I've investigated Maven as a depdendency manager for work and it's still a ways from what I'd call infrastructure. That may change, Maven is highly active.

I'm not saying it shouldn't be a top level project, just curious why it is, or perhaps why it's not in Jakarta. Given that it's far from baked in my humble opinion, depends on non-top level stuff like Jelly and about all you can do with it is manage Java project dependencies. What's the ASF community's rationale for this?


August 8, 2003 10:24 AM

Comments

Carlos
(August 8, 2003 01:08 PM #)

I guess its because James Strachan in an active participant in Geronimo and Maven.

Anyway, can you be a bit more specific about your complaints on Jelly?

Carlos

Bill de hra
(August 8, 2003 01:24 PM #)

I'm pretty sure it doesn't come down to one person Carlos :) As for Jelly, it's not a complaint (not here anyway, that's for another day). I'm just trying to understand how Maven moves to a top level when stuff like Tomcat stays part of Jakarta. Ant I nearly understand since it is infrastructure, even if it is java-centric. Maybe I don't understand how the ASF works.

Andy
(August 8, 2003 01:26 PM #)

The ASF would like to see Jakarta go away, never again create a language-centric project and all projects become more or less TLPs. Projects in Jakarta can generally ask to become TLPs when they feel they are ready. I personally understand the reasoning for this, but I'm not sure I agree. I fought pretty hard to make it voluntary when this decision was made. -Andy

Trackback Pings

TrackBack URL for this entry:
http://www.dehora.net/mt/mt-tb.cgi/1059