> -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.
Sounds good. I'll try and make it a long-term plan of mine to have a Core
jar which hopefully can replace my own current GenJavaCore jar which I
tend to use on all projects I'm on. Once this seems powerful enough, I'll
try to push for it to be created along with individual project jars.
Pluses for me here are:
1) I get something that other people help build. So it'll be N times
better.
2) I get away from the slightly difficult situation of changing my own
open source code on a commercial project and then resubmitting it back to
myself. Technically it seems fine, but it's open for misunderstanding I
think.
3) It's much easier to convince other people to use it.
Bay
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
