On 19 Nov 2003, at 00:12, Henri Yandell wrote:
Sounds entirely feasible.
I'm not sure Tomcat would be too stunned at moving out, as Jakarta has a
lot of brand recognition for them [the years of people thinking Jakarta
was a web server].
One of the reasons for sorting out Apache-Commons vs Jakarta Commons is that it's holding up the movement of the regexps, ecs and bcel inside a more active community.
ecs is truly mature - it does what it does pretty well but IMHO it's a deadend for future development. it's used (quite extensively) in production which is why we fix the occasional bug and very occasionally make a release.
IMHO bcel is also pretty mature and it may (or may not) be complete. there are a lot of exciting, active projects related to bcel but they are not bcel.
IMHO there is very little to gain from moving either project here. they are very easy to oversee (since they are pretty much completed) and seem very happy to slumber. (if either of these came alive again then i'd probably advocate making the change.)
regex and ORO are more active and probably aren't completed (in the way that ecs and bcel probably are). there are problems of procedure and community with them remaining at jakarta. yes - with a bit of effort - the jakarta-pmc could probably solve these issues but maybe a move would be a better (as well as easier) solution. i'm not really sure that jakarta-commons verses apache-commons needs to be resolved before ORO and regex could move.
- robert
