Hi Willem,

can you please elaborate your explanation a bit? Currently what we've on the
2.12.x. as well as 2.11.x branches is this:

    <cxf-version>2.7.10</cxf-version>
    <cxf-version-range>[2.6,2.9)</cxf-version-range>

Now to my understanding this should become:

    <cxf-version>2.7.10</cxf-version>
    <cxf-version-range>[2.6,3)</cxf-version-range>

I think the current range is a problem for the OSGi folks because if e.g.
there's a bug-fix being provided in CXF 2.7.10, currently they can't force
the Container to make use of CXF 2.7.10 while they install the "camel-cxf"
feature version 2.12.3 or 2.11.4 (e.g. in the context of a dependency of
their own Karaf feature "my-cool-app-karaf-feature") because the current
range does NOT include 2.7.10.

Babak


Willem.Jiang wrote
> There are some patches of supporting CXF 3.x are not merged to
> camel-2.12.x and camel-2.11.x.
> So the cxf version rang of camel-2.12.x and camel-2.11.x is right.
> 
> I don’t think it’s a show-stopper.
> 
> --  
> Willem Jiang
> 
> Red Hat, Inc.
> Web: http://www.redhat.com
> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
> (English)
> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang  
> Weibo: 姜宁willem
> 
> 
> 
> On February 16, 2014 at 11:35:56 PM, Babak Vahdat (

> babak.vahdat@

> ) wrote:
>>  
>> O.K. the build has been definetly done using Java 6 as this's how  
>> MANIFEST.MF
>> of camel-core-2.12.3.jar looks like:
>>  
>> Manifest-Version: 1.0
>> Bnd-LastModified: 1392475192207
>> Build-Jdk: 1.6.0_45
>> Built-By: hadrian
>> ...
>>  
>>  
>> Other than that the backport of the fix for CAMEL-7170 did NOT  
>> adjust the
>> maven property accordingly, so on the  
>> master branch
>> we've got:
>>  
>> 2.7.10
>> [2.6,4.0)
>>  
>> Which is fine, however on the 2.12.x as well as the 2.11.x branch  
>> we've got:
>>  
>> 2.7.10
>> [2.6,2.9)
>>  
>> So here's my -1
>>  
>> Babak
>>  
>>  
>> Babak Vahdat wrote
>> > Hi
>> >
>> > The HTML component documentation inside the JARs are missing.  
>> I assume
>> > Java 6 has been used for building this release candidate. See  
>> also the
>> > first "Note" @ http://camel.apache.org/release-guide.html  
>> >
>> > Babak
>> > hadrian wrote
>> >> This is a vote to release Apache Camel 2.12.3, a patch release  
>> coming
>> >> with about 128 issues fixed.
>> >>
>> >> Release notes:
>> >>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>>   
>> >>
>> >> Staging repo:
>> >> https://repository.apache.org/content/repositories/orgapachecamel-1002  
>> >>
>> >> Tarballs:
>> >>
>> https://repository.apache.org/content/repositories/orgapachecamel-1002/org/apache/camel/apache-camel/2.12.3/
>>   
>> >>
>> >> Tag:
>> >>
>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=4bf31d2e2cbc34fda60d68c0dd33cb39d63ba1c6
>>   
>> >>
>> >> Please test this release candidate and cast your vote.
>> >> [ ] +1 Release the binary as Apache Camel 2.12.3
>> >> [ ] -1 Veto the release (provide specific comments)
>> >> Vote is open for at least 72 hours.
>> >>
>> >> Thanks,
>> >> Hadrian
>>  
>>  
>>  
>>  
>>  
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
>>   
>> Sent from the Camel Development mailing list archive at Nabble.com.  
>>





--
View this message in context: 
http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747421.html
Sent from the Camel Development mailing list archive at Nabble.com.

Reply via email to