You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Christian Schneider <ch...@die-schneider.net> on 2014/06/13 10:39:15 UTC
Status of the build
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
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: Status of the build
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Dan,
1/ I agree for the parent: I will change to 2.0.0-SNAPSHOT and update
the modules
2/ for the ASM import range, as I did for slf4j, we can "extend" the
version range. It should be enough.
3/ I will check and update the versioning plugin too.
Thanks for the feedback.
Regards
JB
On 06/16/2014 07:01 PM, Daniel Kulp wrote:
>
> On Jun 15, 2014, at 1:37 PM, Jean-Baptiste Onofré <jb...@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é
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Status of the build
Posted by Daniel Kulp <dk...@apache.org>.
On Jun 15, 2014, at 1:37 PM, Jean-Baptiste Onofré <jb...@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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Status of the build
Posted by Guillaume Nodet <gn...@apache.org>.
Is that a build-time only issue or also a runtime issue ?
I don't have much problem requiring jdk 7 for building but supporting jdk 6
at runtime.
2014-06-16 16:12 GMT+02:00 Christian Schneider <ch...@die-schneider.net>:
> 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" <jp...@gmail.com>:
>
> > 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 <ch...@die-schneider.net>
> > 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é <jb...@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é
> > >> jbonofre@apache.org
> > >> 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
> > >
> >
>
Re: Status of the build
Posted by Christian Schneider <ch...@die-schneider.net>.
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" <jp...@gmail.com>:
> 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 <ch...@die-schneider.net>
> 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é <jb...@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é
> >> jbonofre@apache.org
> >> 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
> >
>
Re: Status of the build
Posted by Jeremy Hughes <jp...@gmail.com>.
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 <ch...@die-schneider.net> 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é <jb...@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é
>> jbonofre@apache.org
>> 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>
Re: Status of the build
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Jeremy,
I wasn't clear.
I think it's good to have JDK 7 for build but still support Java6 for
runtime.
And I think it's the case right now: it fails only in Pax Exam with
Java6 (even if I didn't see that AFAIR).
Regards
JB
On 06/16/2014 11:46 AM, Jeremy Hughes wrote:
> 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é <jb...@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é <jb...@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é
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>
>>>
>>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Status of the build
Posted by Jeremy Hughes <jp...@gmail.com>.
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é <jb...@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é <jb...@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é
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>>
>>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
Re: Status of the build
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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é <jb...@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é
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Status of the build
Posted by Christian Schneider <ch...@die-schneider.net>.
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é <jb...@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é
> jbonofre@apache.org
> 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>
Re: Status of the build
Posted by Jean-Baptiste Onofré <jb...@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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Status of the build
Posted by Daniel Kulp <dk...@apache.org>.
On Jun 13, 2014, at 4:39 AM, Christian Schneider <ch...@die-schneider.net> 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.
This is due to your changes for ARIES-1188.
Those changes removed the ExtraOptions stuff (see your JIRA comment for why), but the builds for some of the modules are still relying on it. Once the scripts updated the poms to grab the latest snapshot of testutils (which has your changes), they fail to compile. Are the failing modules ones that have not yet been updated to pax-exam 3?
Dan
> 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
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Status of the build
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Holly,
thanks for the explanations. Seems I have to learn some more about aries :-)
Is it possible to do the same things the snapshot build does on my local
system? If yes what do I have to do to get the same effects?
Another question: I switched the maven dependencies in pax exam to
.versionAsInProject() as it did not work without that. Does that still
work with the
snapshot build?
Christian
On 13.06.2014 13:56, Holly Cummins wrote:
> The snapshot build is intended to test whether the latest versions of all
> of our modules work with one another. This makes it pretty important. :)
>
> The reason we can't test this in our normal build is that the normal build
> tests modules against the *minimum* level of their dependencies. (This is
> done in the normal build to ensure that the shipped manifests import the
> minimum required level, not the current snapshot.)
>
> For example, if a imports a package from b at version=[1.0,2.0), and b is
> currently at version 1.4-SNAPSHOT, a's pom needs to include a-1.0, not a
> current snapshot. This makes sure that a's manifest imports b with
> version=[1.0, 2.0). The snapshot build for the a module rewrites the pom so
> that we test the latest level of a with the latest level of b. The normal
> build will test the latest level works with the 1.0 level of b.
>
> This is a consequence of having the project composed of many modules, each
> of which are independently releasable. In order to get correct OSGi
> manifests and meaningful test coverage, we need to do a bit more building
> and testing than you'd have to do in a monolithic project.
>
> Holly
>
>
> On Fri, Jun 13, 2014 at 9:39 AM, Christian Schneider <
> chris@die-schneider.net> 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
>>
>> --
>> Christian Schneider
>> http://www.liquid-reality.de
>>
>> Open Source Architect
>> http://www.talend.com
>>
>>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: Status of the build
Posted by Holly Cummins <ho...@googlemail.com>.
The snapshot build is intended to test whether the latest versions of all
of our modules work with one another. This makes it pretty important. :)
The reason we can't test this in our normal build is that the normal build
tests modules against the *minimum* level of their dependencies. (This is
done in the normal build to ensure that the shipped manifests import the
minimum required level, not the current snapshot.)
For example, if a imports a package from b at version=[1.0,2.0), and b is
currently at version 1.4-SNAPSHOT, a's pom needs to include a-1.0, not a
current snapshot. This makes sure that a's manifest imports b with
version=[1.0, 2.0). The snapshot build for the a module rewrites the pom so
that we test the latest level of a with the latest level of b. The normal
build will test the latest level works with the 1.0 level of b.
This is a consequence of having the project composed of many modules, each
of which are independently releasable. In order to get correct OSGi
manifests and meaningful test coverage, we need to do a bit more building
and testing than you'd have to do in a monolithic project.
Holly
On Fri, Jun 13, 2014 at 9:39 AM, Christian Schneider <
chris@die-schneider.net> 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
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
>
Re: Status of the build
Posted by Christian Schneider <ch...@die-schneider.net>.
The localRepository setting should be correct as we would have errors in
the standard build then too.
Christian
On 13.06.2014 14:13, Jean-Baptiste Onofré wrote:
> We also have to check if the getLocalRepo() method is correctly used
> in all itests.
>
> This method checks if the maven.repo.local system property is set and
> uses it, else it falls back to org.ops4j.pax.url.mvn.localRepository.
>
> AFAIR, Jenkins profile provides the maven.repo.local system property
> to point on its local repository (where the SNAPSHOTs have been built).
>
> Regards
> JB
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: Status of the build
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
We also have to check if the getLocalRepo() method is correctly used in
all itests.
This method checks if the maven.repo.local system property is set and
uses it, else it falls back to org.ops4j.pax.url.mvn.localRepository.
AFAIR, Jenkins profile provides the maven.repo.local system property to
point on its local repository (where the SNAPSHOTs have been built).
Regards
JB
On 06/13/2014 02:06 PM, Jean-Baptiste Onofré wrote:
> Hi Christian,
>
> I think the problem is in testunit 2.0.0-SNAPSHOT. It seems that we
> remove some SNAPSHOTs resolution/injection of mavenBundle().
> It allows to have the itests running with all SNAPSHOTs dependencies.
>
> I think it should be fixed in testunit 2.0.0-SNAPSHOT.
>
> 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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Status of the build
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Christian,
I think the problem is in testunit 2.0.0-SNAPSHOT. It seems that we
remove some SNAPSHOTs resolution/injection of mavenBundle().
It allows to have the itests running with all SNAPSHOTs dependencies.
I think it should be fixed in testunit 2.0.0-SNAPSHOT.
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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com