Yes. The compile error only appears for an integration test project and with pax exam classes. Seems the newest version is built for java 7+. It would be great if you could limit the pax exam version to 2.3.4. I will ask on the ops4j list if this is intentional.
Best regards Christian Am 16.06.2014 11:03 schrieb "Jeremy Hughes" <[email protected]>: > Hi Christian, so what is the error with Java 6? Does it only appear > when moving to pax exam 3? Do you think there might be an issue with > pax exam 3 and Java 6? We could override the pax exam level to one > that works with Java 6 and 7 (if that exists :-) > > On 16 June 2014 05:20, Christian Schneider <[email protected]> > 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é <[email protected]>: > > > >> 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é > >> [email protected] > >> http://blog.nanthrax.net > >> Talend - http://www.talend.com > >> > > > > > > > > -- > > -- > > Christian Schneider > > http://www.liquid-reality.de > > < > https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.liquid-reality.de > > > > > > Open Source Architect > > http://www.talend.com > > < > https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.talend.com > > >
