Hi Willem,
thanks. The full test is blue again :-)

regards, aki

2014-06-17 15:42 GMT+02:00 Willem Jiang <willem.ji...@gmail.com>:
> I just changed the configuration, now it is build with latest JDK7.
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> Web: http://www.redhat.com
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.iteye.com (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
> On June 17, 2014 at 9:34:03 PM, Aki Yoshida (elak...@gmail.com) wrote:
>> Hi Babak,
>> thanks for the detail.
>>
>> In that case, I hope someone is doing the change for the master build soon. 
>> :-)
>>
>> regards, aki
>>
>>
>> 2014-06-17 15:21 GMT+02:00 Babak Vahdat :
>> > Hi Aki
>> >
>> > For 2.14.0 currently there's an ongoing attempt to suppor JDK 8
>> > https://issues.apache.org/jira/browse/CAMEL-7314
>> >
>> > And looking back into the Camel releases in the past, each given release
>> > *typically* does support 2 JDKs so that when 2.14.0 is out then we would
>> > support both JDK 7 and 8 and can drop supporting JDK 6 as the release notes
>> > says this:
>> > http://camel.apache.org/camel-2140-release.html#Camel2.14.0Release-Importantchangestoconsiderwhenupgrading
>> >
>> > I guess what still needs to be done as well is to tweak the
>> > maven-compiler-plugin settings on master for source/target (1.6 => 1.7)
>> >
>> > Regarding the build failures you mentioned, there was an old attempt to
>> > stabilize it
>> > https://issues.apache.org/jira/browse/INFRA-6218
>> >
>> > Babak
>> >
>> > Aki Yoshida-3 wrote
>> >> 2014-06-13 12:43 GMT+02:00 Babak Vahdat <
>> >
>> >> babak.vahdat@
>> >
>> >> >:
>> >>>
>> >>>
>> >>> Am 13.06.14 12:23 schrieb "Aki Yoshida" unter <
>> >
>> >> elakito@
>> >
>> >> >:
>> >>>
>> >>>>I noticed the full test has been red for some time at camel-barcode.
>> >>>>
>> >>>>Today, I noticed that this test is using mvn:com.google.zxing/core/3.0.0
>> >>>>and this core-3.0.0.jar was built with jdk 7
>> >>>>
>> >>>>so it can't be used with the current jdk6 camel build.
>> >>>
>> >>> I guess the JDK6 support is dropped by the upcoming 2.14.0 release so
>> >>> that
>> >>> we should be fine here.
>> >>
>> >> Hi,
>> >> the full test is still red.
>> >> https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.fulltest/
>> >>
>> >> and the full test with jdk7 is disabled and hasn't run for almost 6
>> >> months.
>> >> https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.fulltest.java7/
>> >>
>> >> Something needs to be done here.
>> >>
>> >> I am not sure about Babak's statement about 2.14 dropping JDK6
>> >> support. Does this mean it will be really dropped or the regular build
>> >> will be switched to JDK7 but using the compliance level to 6? I
>> >> remember Willem has used JDK7 for the release build but with the
>> >> compliance set to 6.
>> >>
>> >> I seem to remember having some conversation about JDK version update
>> >> for Camel but I may be confused with what we discussed for CXF
>> >> (dropping of 6 in 3.1.0 and this is also documented in the CXF FAQ). I
>> >> couldn't find any relevant information for Camel.
>> >>
>> >> thanks.
>> >>
>> >> regards, aki
>> >>
>> >>
>> >>
>> >>
>> >>>
>> >>> Babak
>> >>>
>> >>>>
>> >>>>I don't know if there is a jdk6 compatible jar.
>> >>>>Or else the test should be disabled for jdk6.
>> >>>>
>> >>>>regards, aki
>> >>>
>> >>>
>> >
>> >
>> >
>> >
>> >
>> > --
>> > View this message in context: 
>> > http://camel.465427.n5.nabble.com/jenkins-full-test-build-error-at-camel-barcode-tp5752260p5752437.html
>> > Sent from the Camel Development mailing list archive at Nabble.com.
>>
>

Reply via email to