Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of willem.jiang@gmail.com
 designates 209.85.142.186 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:x-enigmail-version:content-type
         :content-transfer-encoding;
        b=WoFSciL6D0vv31Uu9h7pxTWPCzkL66+/jh0S1+FPvAjs2JPAPqxRmxet8clUGP8FKP
         OXXPc9UqzUwdvEKBMADeQsGX06KtrQ9K3nHWn/IKL7k0ekbV84qpQqyc3fnpAPNgMYgR
         04zzMgZBuBt4iILOS8Pf9Ptdp7hsT2pADNjCA=
Message-ID: <4994C5A7.4020002@gmail.com>
Date: Fri, 13 Feb 2009 08:58:15 +0800
From: Willem Jiang <willem.jiang@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: dev@camel.apache.org
Subject: Re: svn commit: r743645 - /camel/trunk/pom.xml
References: <20090212080209.7884623889BB@eris.apache.org>
 <eeacbf0c0902120737q1bd8bdeft49b8f008f8e93c09@mail.gmail.com>
 <CACB8059-A2C2-496B-9EB0-7703A189C293@gmail.com>
In-Reply-To: <CACB8059-A2C2-496B-9EB0-7703A189C293@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi

I don't realize that camel-cxf will need CXF 2.2 snapshot for adding the
Jaxrs 1.0 support, so I changed the CXF version to new released 2.1.4.

Basically I don't want to camel-cxf stick to CXF 2.2, can we support CXF
2.2.x and CXF 2.1.x at the same time ?

As Hadrian said , we should not release a kit without any dependency of
SNAPSHOT. But for the working in progress Camel 2.0-SNAPSHOT, it should
be OK, we can resolve this issue before we release Camel 2.0.

Willem


Hadrian Zbarcea wrote:
> 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,  <ningjiang@apache.org> 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>
>>>
>>>
>>>
> 
>