> been fixed since 1.2.0 (we so need 1.3.0 to be released! :)
>

Wouldn't it be possible to have milestone-releases?

Right now we are using 1.2.0, and many of the problems we have are fixed in
1.3.0-SNAPSHOT. But if I change the maven build to use the snapshot, it will
check for new versions every now and then, and that is something I don't
want. I don't want to spend hours debugging my app just because todays
snapshot-build of camel might be broken.

Using a fixed milestone-release of 1.3 on the other hand, would be no
problem.

So go change 1.3.0-SNAPSHOT to 1.3.0-m1, mvn deploy, and change back to
1.3.0-SNAPSHOT and continue woking on all the great stuff! :-)

-- 

 /Magnus Heino

Reply via email to