Hi, it's true that Oracle's Java 6 is EOL. There are other vendors, such as IBM who haven't EOL'd Java 6 yet:
According to https://www.ibm.com/developerworks/java/jdk/lifecycle/index.html they will service it until Sep 2017. I'd like to make sure we can continue to run / test on Java 6 until then. Zero Turnaround's latest survey (published 21 May 2014) here: http://zeroturnaround.com/rebellabs/java-tools-and-technologies-landscape-for-2014/ the Java SE usage is: Java 5: 2% Java 6: 26% Java 7: 65% Java 8: 7% Would be good to have separate Jenkins jobs for that so something we still run on Java 6. I think I saw other projects that have build jobs specifically for IBM Java SDKs. I can look into setting that up. btw: you may be thinking "well Jeremy works for IBM so he would say that" ... it's true I do. I don't work on the Java SDK but I do work on projects that use it. I think there's still a lot of usage of Java 6 out there so I'd like to ensure we still run on it. Thanks, Jeremy On 16 June 2014 05:47, Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > IMHO, Java7 is OK (as Java6 is EOL). > > Regards > JB > > > On 06/16/2014 06:20 AM, Christian Schneider wrote: >> >> Also short update from my side. >> >> I finished the transition to pax exam 3. >> The original compile Problem in the aries build with snapshots disappeared >> then. I got another failure though as the build seems to use the newest >> Version of pax exam too (not sure why). This version seems to fail with >> java 6. So I bumped up the java version of this build. Unfortunately I hit >> another compile Problem at a later point. I will continue to investigate >> this. >> >> Is it ok to compile with Java 7 or should I try to reset to java 6? >> >> Christian >> >> >> 2014-06-15 19:37 GMT+02:00 Jean-Baptiste Onofré <j...@nanthrax.net>: >> >>> Hi, >>> >>> just an quick update: >>> - I updated all modules to asm5 except ejb (I have to check the openejb >>> version supporting asm5/java8 for the itests). >>> - we have a full build (including itests) running with java6 and java7 >>> - java8 just fails for ejb* itests (due to asm4/xbean usage) >>> - I will add JPA 2.1 support tonight >>> >>> I would propose to prepare a set of releases for ASM5/Java8 support, in >>> the following order: >>> 1/ "new" parent pom 1.0.1 >>> 2/ proxy-impl 1.0.3 >>> 3/ proxy-bundle 1.0.2 >>> 4/ followed by in any order: >>> application-converters >>> application-tooling-repository-generator >>> web-urlhandler >>> blueprint-core >>> blueprint-bundle >>> blueprint-annotation-impl >>> spi-fly* >>> >>> If there is no objection, I would like to start the releases as soon as >>> the JPA 2.1 support is completed (so I propose Tuesday). >>> >>> WDYT ? >>> >>> >>> Regards >>> JB >>> >>> On 06/13/2014 10:39 AM, Christian Schneider wrote: >>> >>>> The normal aries build as well as the deploy build seem to be stable >>>> again. >>>> See >>>> https://builds.apache.org/view/A-D/view/Aries2/job/Aries/ >>>> >>>> The build with snapshot dependencies seems to continually fail. >>>> https://builds.apache.org/view/A-D/view/Aries2/job/ >>>> AriesWithSnapshotDependencies/ >>>> >>>> >>>> The build fails during the application integration tests with a compile >>>> error. >>>> >>>> Unfortunately I do not fully understand what the failing build does >>>> exactly. Can someone explain how this build works and perhaps give some >>>> advice what is going wrong at the moment? >>>> I would like to do a build on my own system that replicates the same >>>> errors but have no idea how to do this. >>>> >>>> Maybe this build simply does not work anymore with the new integration >>>> tests as I now use .versionAsInProject in pax exam while I think the old >>>> tests used a different mechanism to determine the version of >>>> dependencies. >>>> >>>> Christian >>>> >>>> >>> -- >>> Jean-Baptiste Onofré >>> jbono...@apache.org >>> http://blog.nanthrax.net >>> Talend - http://www.talend.com >>> >> >> >> > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com
