Nope. We had a similar discussion on the mailing lists more than a
year ago, and the consensus was that dependencies on a SNAPSHOT is a
no-no.
First off, we cannot release with a dependency on a SNAPSHOT, a user
downloading a kit a while after the release may not have a snapshot
available, or there may be incompatibilities rendering our kit
useless. Second, by depending on a snapshot, changes in that snapshot
may break our builds unexpectedly, impacting our productivity. If we
absolutely need to use features in from an unreleased project (and it
happened in the past) we have a few options: (1) wait until the
release and make the updates then, (2) produce our own internal
release, publish it in our repo and use that.
Cheers
Hadrian
On Feb 12, 2009, at 10:37 AM, William Tam wrote:
Is it ok to leave the trunk to depend on cxf 2.2-SNAPSHOT? I'm trying
to add Jaxrs 1.0 support to camel-cxf which requires 2.2 snapshot.
On Thu, Feb 12, 2009 at 3:02 AM, <[email protected]> wrote:
Author: ningjiang
Date: Thu Feb 12 08:02:09 2009
New Revision: 743645
URL: http://svn.apache.org/viewvc?rev=743645&view=rev
Log:
CAMEL-1333 updated the cxf version to 2.1.4
Modified:
camel/trunk/pom.xml
Modified: camel/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/camel/trunk/pom.xml?rev=743645&r1=743644&r2=743645&view=diff
=
=
=
=
=
=
=
=
=
=====================================================================
--- camel/trunk/pom.xml (original)
+++ camel/trunk/pom.xml Thu Feb 12 08:02:09 2009
@@ -43,7 +43,7 @@
<!-- Note that activemq dependency is only used for testing! -->
<activemq-version>5.2.0</activemq-version>
<apacheds-version>1.5.4</apacheds-version>
- <cxf-version>2.2-SNAPSHOT</cxf-version>
+ <cxf-version>2.1.4</cxf-version>
<felix-version>1.4.1</felix-version>
<felix-osgi-version>1.2.0</felix-osgi-version>
<httpcore-version>4.0-beta3</httpcore-version>
