-1 - we don't have the parallel release cycle to pull this off. We'll all be stuck because commons doodah has no reason to upgrade and no one active on it.
I'm +1 to upgrading all the dependencies though - I wouldn't even think it needs a vote. Just dig in and upgrade all the dependencies you see (on all 3 build systems) and check they still compile. Then check it in. That's why I'm miffed about the commons-parent thing - it's broken the components because the job hasn't been finished by updating the pom.xmls. I know it's probably because it can be easy to view Commons Xxxx as Fred's baby, but it's one big codebase and you can go dive in and do cross-commons things that seem to be common sense and apologise later - or raise an all thread to discuss (kind of like below) and then dive in. Hen On 11/1/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
Speaking of cross-commons, the JCL deps are all over the place. Which is probably OK for now, since most variants are point releases (1.0, 1.0.2, 1.0.3, 1.0.4 being popular ATM). Since JCL is the bottom rung of the ladder, we should do our bit and move as one (i.e. if a component wants to up the JCL version, it should be an [all] discussion, and all components should update trunk such that their next RC matches up). We could restrict this to minor or major release updates, but I don't see any harm in keeping the JCL point release consistent as well. [ ] +1 Sounds reasonable [ ] 0 [ ] -1 Sounds unreasonable -Rahul --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
