On Sun, 22 May 2005, Adam R. B. Jack <[EMAIL PROTECTED]> wrote: > Does it make sense to move public (with nagging) to JDK 1.5?
Not yet, IMHO. > Given that we can't support all configurations, and given the level > of turmoil the JAXP 1.3 seems to be causing, ought we not just dive > in w/ both feet & embrace change? I find this time quite interesting since we see projects embrace JAXP 1.3 and in particular DOM3 at very different paces. > Since (I believe) JDK ought be compile compatible w/ older JDKs, Do you really belive this was true? Or is this just what you whish would be true? ;-) > Seems relatively healthy, and not too painful. That said, I'm not > expert, I'm just asking a question. If you look through the latest JDK 1.5 Gump runs you'll see a few projects which look more or less dead (jython) but don't build and are important in Gump's chain. Switching to JDK 1.5 now may cause the projects that don't build because they are specifiying an incompatible combination of -source and -target or don't specify -source at all to improve. It may also lead to projects rethinking their dependencies, but probably not (they'll simply not notice that their won project doesn't get built at all). All in all I think we'd drop the number of projects we build every night considerably with no real hope to get back quickly. So I'm rather +/-0 to the idea (not -1 since I don't believe our chances would improve too much if we'd wait any longer either). Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
