> Thanks for doing some preliminary checks. Like I said, I'm not against > it, in fact I think I have an open issue somewhere to upgrade :)
Damn, I probably filed a duplicate then. > I could also test some platforms and especially packaging. Not to worry, I can do this -- run a task, change a diaper, run a task, change a diaper. Good we have long-running targets. > I just want us to be careful before upgrading, and when we do it, we > should upgrade the ant on jenkins and all that to the version we > intend to support. Its a symlink so we can keep the old one in case > all hell breaks loose ... I'll check everything locally first and once checked we can substitute on jenkins. I don't think there will be any difference other than unexpected things like different memory requirements (OOMs, permgens). > We should also think about which bugfix level of 1.8 we require. I > know a version of 1.8.x (not sure which one) ships by default on mac, > which may have urged David to start questioning why we have this > verbage. will any of the 1.8's work? or do we need 1.8.1 as a minimum, > etc, because of some bugs that would break things. Definitely not the early ones because they were buggy. 1.8.3 seems relatively fresh (February 29th, 2012), so I'd say 1.8.2 (2010-12-20)? This is a long delay from 1.8.2 to 1.8.3... just peeked at the rel. notes and there are issues that could affect us: https://issues.apache.org/bugzilla/show_bug.cgi?id=48789 I also don't object to just saying 1.8.3 is the minimum required version. It's the trunk after all -- it'll be a month or two (ehm) before it is released so 1.8.3 will be a de-facto standard? Dawid --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
