Am 18.06.14 15:54 schrieb "Babak Vahdat" unter <babak.vah...@swissonline.ch>:
> > >Am 18.06.14 14:16 schrieb "Aki Yoshida" unter <elak...@gmail.com>: > >>yes. We have been having this http proxy 503 error in all notest >>builds for some days. I don't know what the problem is. > >The snapshot repo was done but now it's up & back again, so hopefully the >next build will look a bit better: done => down > >https://repository.apache.org/content/repositories/snapshots/ > > >> >>by the way, just came another build error from trunk.fullest.spring4 >>https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.fulltest.sp >>r >>ing4/ >>this build job also needs to switch to jdk7. > >Is done and also kicked a new build to see how it would go now. > >Babak > >> >>regards, aki >> >> >> >>2014-06-18 12:56 GMT+02:00 Babak Vahdat <babak.vah...@swissonline.ch>: >>> Hi >>> >>> Not that it would be something new at all but the last builds of the >>>2.13.x >>> branch without running tests: >>> >>> >>>https://builds.apache.org/view/All/job/Camel.2.13.x.notest/14/consoleTex >>>t >>> >>>https://builds.apache.org/view/All/job/Camel.2.13.x.notest/13/consoleTex >>>t >>> >>> Ended up with weird HTTP 502 or 503 status codes like: >>> >>> org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed >>>to >>> retrieve remote metadata >>> org.apache.camel.karaf:apache-camel/maven-metadata.xml: Could not >>>transfer >>> metadata org.apache.camel.karaf:apache-camel/maven-metadata.xml from/to >>> apache.snapshots.https >>> (https://repository.apache.org/content/repositories/snapshots): Failed >>>to >>> transfer file: >>> >>>https://repository.apache.org/content/repositories/snapshots/org/apache/ >>>c >>>amel/karaf/apache-camel/maven-metadata.xml. >>> Return code is: 502 , ReasonPhrase:Proxy Error. >>> at >>> >>>org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defaul >>>t >>>ArtifactDeployer.java:143) >>> at >>> >>>hudson.maven.reporters.MavenArtifactRecord.deploy(MavenArtifactRecord.ja >>>v >>>a:193) >>> at >>>hudson.maven.RedeployPublisher.perform(RedeployPublisher.java:176) >>> at >>>hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) >>> at >>> >>>hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild. >>>j >>>ava:804) >>> at >>> >>>hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(A >>>b >>>stractBuild.java:776) >>> at >>> >>>hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(Mave >>>n >>>ModuleSetBuild.java:1040) >>> at >>> >>>hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.jav >>>a >>>:725) >>> at hudson.model.Run.execute(Run.java:1701) >>> at >>>hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) >>> at >>>hudson.model.ResourceController.execute(ResourceController.java:88) >>> at hudson.model.Executor.run(Executor.java:231) >>> >>> Babak >>> >>> Aki Yoshida-3 wrote >>>> Hi Willem, >>>> thanks. The full test is blue again :-) >>>> >>>> regards, aki >>>> >>>> 2014-06-17 15:42 GMT+02:00 Willem Jiang < >>> >>>> willem.jiang@ >>> >>>> >: >>>>> 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 ( >>> >>>> elakito@ >>> >>>> ) 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-Im >>>>>>p >>>>>>ortantchangestoconsiderwhenupgrading >>>>>> > >>>>>> > 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.fulltes >>>>>>t >>>>>>/ >>>>>> >> >>>>>> >> 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.fulltes >>>>>>t >>>>>>.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-ca >>>>>>m >>>>>>el-barcode-tp5752260p5752437.html >>>>>> > Sent from the Camel Development mailing list archive at >>>>>>Nabble.com. >>>>>> >>>>> >>> >>> >>> >>> >>> >>> -- >>> View this message in context: >>>http://camel.465427.n5.nabble.com/jenkins-full-test-build-error-at-camel >>>- >>>barcode-tp5752260p5752499.html >>> Sent from the Camel Development mailing list archive at Nabble.com. > >
