Hadrian canceled the release [1]. This means the existing tag will be replaced by a new one. So we have to wait for this one...
Running camel-extra against Camel 2.10.0 is done in a few seconds. Tagging it also. I don't see the advantage not to wait until Camel 2.10.0 is released. The only thing I (or someone else) has to figure out is how we signe our artifacts and to which repo we want to upload it. [1] http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-10-0-td5714768.html Best, Christian On Wed, Jun 27, 2012 at 1:10 PM, Henryk Konsek <hekon...@gmail.com> wrote: > > When we tag camel-extra 2.10.0, we have to update the version to 2.10.0 > in > > camel-extra too. For this, we need the Camel 2.10.0 artifacts (not only > in > > a staging repo). This is the dependency I have in mind. > > Actually I thought that we could just build+install the Camel 2.10 > locally (from 2.10 tag) and work against artifact from our local > repository. Then, after the Camel 2.10 is in central, we could remove > our local 2.10 artifacts and verify that our Camel-Extra tag can be > built against Camel artifacts from central. > > I aware that in pessimistic case this approach will require us to > update SVN tag, what is technically possible but not respects the > immutability of the tag. But it speeds things up :) . > > > About uploading the artifacts (including the signatures), I don't know > > whether this works already out of the box. I doubt, but will check it > next > > week... > > Yeah, we could investigate (and probably fix it) later. > > -- > Henryk Konsek > http://henryk-konsek.blogspot.com >
