Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Message-ID: <539DD9E2.7040503@nanthrax.net>
Date: Sun, 15 Jun 2014 19:37:38 +0200
From: =?ISO-8859-1?Q?Jean-Baptiste_Onofr=E9?= <jb@nanthrax.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: dev@aries.apache.org
Subject: Re: Status of the build
References: <539AB8B3.5000208@die-schneider.net>
In-Reply-To: <539AB8B3.5000208@die-schneider.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Hi,

just an quick update:
- I updated all modules to asm5 except ejb (I have to check the openejb=20
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=20
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=20
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 ag=
ain.
> 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/AriesWithSnapshotDep=
endencies/
>
>
> 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 som=
e
> 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 ol=
d
> tests used a different mechanism to determine the version of dependenci=
es.
>
> Christian
>

--=20
Jean-Baptiste Onofr=E9
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com