-p14917200s22882.html
Thanks,
Arjan
--
View this message in context:
http://www.nabble.com/Apache-Camel-1.3.0-RC2-is-out-tp15771987s22882p15871609.html
Sent from the Camel - Users mailing list archive at Nabble.com.
The version is 1.3.0. This is a second try, but it will be promoted
to 1.3.0 if everything is ok.
Just use the 1.3.0 version and point to the repo and it should work.
On Mon, Mar 3, 2008 at 12:49 PM, Magnus Heino [EMAIL PROTECTED] wrote:
Why are the jars and poms named 1.3.0 and not
On 03/03/2008, Magnus Heino [EMAIL PROTECTED] wrote:
Why are the jars and poms named 1.3.0 and not 1.3.0-RC2??? Makes them not so
usable, atleast not in my environment :-P
The idea is once we've voted on a release, it becomes the final 1.3.0
release - without having to cut another release
Yes, but if I add this to our company wide Artifactory proxy, people will
start downloading it as 1.3.0
If you then change it, and still label it 1.3.0, noone will notice, and I
will have to inform people to manually delete it from their local
repositories.
/Magnus
On Mon, Mar 3, 2008 at 12:55
Yeah, I agree. I think it was a bad idea to advertise it on the users list.
At least, there should have been a big warning that this is not yet an official
release.
On Mon, Mar 3, 2008 at 1:04 PM, Magnus Heino [EMAIL PROTECTED] wrote:
Yes, but if I add this to our company wide Artifactory
On 03/03/2008, Magnus Heino [EMAIL PROTECTED] wrote:
Yes, but if I add this to our company wide Artifactory proxy, people will
start downloading it as 1.3.0
If you then change it, and still label it 1.3.0, noone will notice, and I
will have to inform people to manually delete it from their
Hi,
After a long and painful labor the baby is out. Thanks to the many
contributors and a growing community with have 133 issues resolved in
this version and a stable product.
Please find the binary distribution here:
http://people.apache.org/~hadrian/apache-camel-1.3.0-RC2/maven2
and the
