Hi Hadrian, The build is succeed in my windows box, I think you can kick off the release process now :)
Cheers, Willem Willem Jiang wrote: > Hi Hadrian, > > I just fixed the build error, now I'm running the tests on my windows box. > > Willem > > Willem Jiang wrote: >> Hi Hadrian, >> >> Don't worry, this is my turn (working in the morning now). >> I will keep you posted if I resolve this issue. >> >> Cheers, >> >> Willem >> >> Hadrian Zbarcea wrote: >>> I figured that you only hit that issue if you do a release:prepare >>> without building first, but now I hit another one (below). This seems >>> easy to fix, a recent api change, but it's really late and I'll continue >>> in the morning. >>> >>> Hadrian >>> >>> >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Building Camel :: Ruby >>> [INFO] task-segment: [install] >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] [resources:resources] >>> [INFO] Using default encoding to copy filtered resources. >>> [INFO] [compiler:compile] >>> [INFO] Compiling 2 source files to >>> /w1/apache/release/camel/components/camel-ruby/target/classes >>> [INFO] >>> ------------------------------------------------------------------------ >>> [ERROR] BUILD FAILURE >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Compilation failure >>> /w1/apache/release/camel/components/camel-ruby/src/main/java/org/apache/camel/ruby/ScriptRouteBuilder.java:[50,31] >>> to(java.lang.String) in org.apache.camel.ruby.ScriptRouteBuilder cannot >>> override to(java.lang.String) in >>> org.apache.camel.builder.BuilderSupport; attempting to use incompatible >>> return type >>> found : org.apache.camel.model.ProcessorDefinition >>> required: org.apache.camel.builder.ValueBuilder >>> >>> >>> >>> /w1/apache/release/camel/components/camel-ruby/src/main/java/org/apache/camel/ruby/ScriptRouteBuilder.java:[50,31] >>> to(java.lang.String) in org.apache.camel.ruby.ScriptRouteBuilder cannot >>> override to(java.lang.String) in >>> org.apache.camel.builder.BuilderSupport; attempting to use incompatible >>> return type >>> found : org.apache.camel.model.ProcessorDefinition >>> required: org.apache.camel.builder.ValueBuilder >>> >>> >>> >>> >>> >>> >>> >>> On Jun 2, 2009, at 6:03 PM, Hadrian Zbarcea wrote: >>> >>>> Hi, >>>> >>>> I am roaming through Europe with net connectivity only in the evening >>>> at the hotel. The release process takes a few hours and I couldn't >>>> complete it last week as I planned due to errors I hit. I fixed the >>>> checkstyle issues, but now I hit a new one attempting to release again >>>> (see below). It's a circular dependency introduced in the past days, >>>> which you may not see if you don't remove camel from the local maven >>>> repo and rebuild from scratch. It's past midnight now. If I won't >>>> figure it out in the next minutes I'll work on it again in the morning. >>>> >>>> Cheers, >>>> Hadrian >>>> >>>> >>>> Missing: >>>> ---------- >>>> 1) org.apache.camel:camel-core:test-jar:tests:2.0-SNAPSHOT >>>> >>>> Try downloading the file manually from the project website. >>>> >>>> Then, install it using the command: >>>> mvn install:install-file -DgroupId=org.apache.camel >>>> -DartifactId=camel-core -Dversion=2.0-20090409.130820-13 >>>> -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file >>>> >>>> Alternatively, if you host your own repository you can deploy the >>>> file there: >>>> mvn deploy:deploy-file -DgroupId=org.apache.camel >>>> -DartifactId=camel-core -Dversion=2.0-20090409.130820-13 >>>> -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file >>>> -Durl=[url] -DrepositoryId=[id] >>>> >>>> Path to dependency: >>>> 1) org.apache.camel:camel-spring:bundle:2.0-SNAPSHOT >>>> 2) org.apache.camel:camel-core:test-jar:tests:2.0-SNAPSHOT >>>> >>>> >>>> >>>> >>>> >>>> >>>> On Jun 2, 2009, at 1:38 AM, Claus Ibsen wrote: >>>> >>>>> Hi Hadrian >>>>> >>>>> Do you have a minute to comment when you have time to do a 2.0m2 >>>>> release? >>>>> If you do not have the time, do you think I (or Jonathan) have >>>>> sufficient privileges to try doing the release? >>>>> >>>>> Its important that we get a 2.0m2 out of the door now. We have approx >>>>> 200 tickets fixed since 2.0m1 and there >>>>> have been major work done, so its important to give the community time >>>>> to test drive it before we start finalizing and doing a RC cut. >>>>> >>>>> >>>>> >>>>> On Mon, May 25, 2009 at 9:38 AM, Claus Ibsen <[email protected]> >>>>> wrote: >>>>>> On Mon, May 25, 2009 at 9:32 AM, S. Ali Tokmen >>>>>> <[email protected]> wrote: >>>>>>> Hello >>>>>>> >>>>>>> Does this mean that CAMEL 2.0-M2 will be based on revision 777408? >>>>>> I think Hadrian will do the 2.0m2 release at any day when he has time. >>>>>> And usually its based on the trunk revision at the time. >>>>>> >>>>>> So if he does it tomorrow then the commits of this day is usually in >>>>>> the 2.0m2 release also. >>>>>> >>>>>> Hadrian your comments? >>>>>> >>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> S. Ali Tokmen >>>>>>> [email protected] >>>>>>> >>>>>>> Office: +33 4 76 29 76 19 >>>>>>> GSM: +33 66 43 00 555 >>>>>>> >>>>>>> Bull, Architect of an Open World TM >>>>>>> http://www.bull.com >>>>>>> >>>>>>> >>>>>>> >>>>>>> Willem Jiang a écrit : >>>>>>>> Hi Hadrain, >>>>>>>> >>>>>>>> I just change the trunk code to use camel internal maven >>>>>>>> repository to >>>>>>>> look up the internal version of spring javaconfig[1]. >>>>>>>> Now we should ready for the Camel 2.0-m2 release :) >>>>>>>> >>>>>>>> [1]https://issues.apache.org/activemq/browse/CAMEL-1635 >>>>>>>> >>>>>>>> Cheers, >>>>>>>> >>>>>>>> Willem >>>>>>>> >>>>>>>> Willem Jiang wrote: >>>>>>>> >>>>>>>>> Hi Hadrain >>>>>>>>> >>>>>>>>> I fixed the build by reverting the spring javaconfig to >>>>>>>>> 1.0-SNAPSHOT. >>>>>>>>> I will setup an internal maven repository in the camel svn >>>>>>>>> repository to >>>>>>>>> hold the latest spring javaconfig. In this way , we can get >>>>>>>>> control of >>>>>>>>> Camel releasing. >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> >>>>>>>>> Willem >>>>>>>>> >>>>>>>>> Hadrian Zbarcea wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> I am ready to issue the 2.0-M2 release, the only problem is that >>>>>>>>>> after >>>>>>>>>> going back to the 1.0 M4 release of javaconfig the tests fail >>>>>>>>>> and didn't >>>>>>>>>> have the time to figure out why. The problem is related to >>>>>>>>>> endpoints >>>>>>>>>> not being injected, afaict. >>>>>>>>>> >>>>>>>>>> I will be flying to Europe now and won't be online probably until >>>>>>>>>> Sat/Sun when I'll build the kit. If anybody can fix those tests >>>>>>>>>> that'd >>>>>>>>>> be great, if not I'll disable the tests and proceed with the >>>>>>>>>> release, as >>>>>>>>>> javaconfig is experimental for the M2 release. >>>>>>>>>> >>>>>>>>>> If anybody disagrees please shout, or even better fix the tests. >>>>>>>>>> >>>>>>>>>> Cheers >>>>>>>>>> Hadrian >>>>>>>>>> >>>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>> >>>>>> -- >>>>>> Claus Ibsen >>>>>> Apache Camel Committer >>>>>> >>>>>> Open Source Integration: http://fusesource.com >>>>>> Blog: http://davsclaus.blogspot.com/ >>>>>> Twitter: http://twitter.com/davsclaus >>>>>> >>>>> >>>>> -- >>>>> Claus Ibsen >>>>> Apache Camel Committer >>>>> >>>>> Open Source Integration: http://fusesource.com >>>>> Blog: http://davsclaus.blogspot.com/ >>>>> Twitter: http://twitter.com/davsclaus >> > >
