I too stick with the Java-centric theme. I don't want to seem overly anti other programming languages, its just that IMO j-c is better of as just Java.
a) Code standards, guidelines, packaging, naming, integration with JDK - all are very Java specific, and are usefully captured in the charter.
b) j-c is already very busy, and if we add BCEL and perhaps some others, (which we probably should), it could get busier.
c) There is no easy division within j-c. I've tried on many occasions to find one, and always fail. However there is the potential for some to leave*
Stephen
I agree with all of these points, and others made by Dirk and Morgan elsewhere on this thread related to the Java community aspects of Jakarta in general and Jakarta Commons in particular. One thing that I would personally be very sad to lose in j-c is the regular comments and discussion from Java developers (many from other Jakarta projects) on Java language-related issues that come up frequently. If we were to lose or dillute the Java-identity of j-c, I am afraid that the signal to noise ratio on the lists might get too low to maintain the interest of some of these folks.
One more point. While I have not participated much in the general@ and pmc@ discussions of where Jakarta may be headed, I think that we can solve the oversight and organization problems without turning all projects into TLPs and I would like to see Jakarta maintain its identity and community, with j-c an important part of both.
Phil
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
