On Jun 15, 2014, at 1:37 PM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
> 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 This new parent pom is a huge change over the way the previous parent poms were setup. I’m going to suggest calling it 2.0.0. Yes, it’s just a parent pom and pretty much irrelevant from a “version” standpoint, but it really is a big change. > 2/ proxy-impl 1.0.3 > 3/ proxy-bundle 1.0.2 Here’s a question……. The proxy bundles (and a bunch of others), now have their ASM import range updated to [5,6) whereas the old versions were [4,5). This does mean they are not a “drop in” replacements for the older bundles. Does that have any impact on what the version number should be for these? Technically, the exported packages are completely compatible, but the imports are not. > 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). Sure. The versioning plugin is “released”, just waiting for it to sync to central. Dan > > 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 -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
