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 >> > >
