----- Original Message ----- From: <[EMAIL PROTECTED]> To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]> Sent: Wednesday, February 20, 2002 11:10 PM Subject: RE: Dependency question
> +1 from me. I've been using the style of mapping my own generic components > to the Java structure for a year now and it's very successful. I suspect a > lot of others have been too. > > Just to throw another spannner in, I just added in the compare/ package of > Comparators that I've been meaning to commit for eons now. > > I'm happy to help on the legwork. Thoe major thing I'm unsure on is how to > make a sub-project dependant on another sub-project. I suspect that > splitting the Utils out into multiple JDK-facing packages will result in > a large level of interdependencies. > > Maybe we should keep the packages separate but consider releasing them > along with Collections and any other pure Java packages as a Commons > release, instead of Utils 1.0, Collections 2.0 etc. Instead an > Apache-Commons-Core 1.0 release would be made. This would hopefully be so > useful that it would be as common in a Java 2 classpath as collections.jar > was in a 1.1 classpath. > > Things like Digester, DBCP, etc would remain their own releases, but they > and any other Jakarta code would quite likely have a dependency on the > core classes. [I seem to be spending the night suggesting increasingly > outlandish ideas, waiting for someone to shut me up :)] > > Bay Biiig +1 for splitting up Util into separate, focused components, if the committers are willing. I've been wanting to suggest that for some time now, but I feared it would be unpopular. Each component will be much higher quality than if they were all maintained together as one generic package. It's also more in line with the ideas behind this project. -1 on the "Apache-Commons-Core" concept though, if I understand the idea correctly. I'd rather see the truly interested parties managing the release cycles of individual components, rather than everyone trying to ride herd over the whole enchilada. It may be a nice convenience to release a single JAR with a certain subset of the components whenever any single component performs a release, but I don't think we should discard versioning and releasing each component individually. I think development is much more focused (and rapid) that way. - Morgan _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
