I figured that's what was going on. Also, I don't think the cxf-version-range property is doing what we think it's supposed to do, perhaps. It's set to [2.6,4.0), but the ranges show up as [2.6,2.9). So, perhaps we need to investigate that? I think CAMEL-7170 can remain "fixed", since it did exactly as it was asked to do, though.
On Mon, Feb 17, 2014 at 8:17 AM, Babak Vahdat <babak.vah...@swissonline.ch> wrote: > You're right and sorry for the confusion. I don't know why, but somehow my > brain treated 2.7.10 as 2.9.10! > > So I change my vote here to +1. > > Babak > > > James Carman wrote >> When I open up the META-INF/MANIFEST.MF file in 2.11.3, I see: >> >> org.apache.cxf;version="[2.6,2.9)" >> >> In this prepared 2.11.4 candidate I see: >> >> org.apache.cxf;version="[2.6,2.9)" >> >> So, nothing appears to have changed there. If we look at the >> feature.xml file in this release candidate: >> <feature name="camel-cxf" version="2.11.4" resolver="(obr)" >> start-level="50"> >> >> <feature version="2.11.4"> >> camel-spring >> </feature> >> >> <feature> >> jetty >> </feature> >> >> <feature version="[2.6,2.9)"> >> cxf >> </feature> >> >> <feature version="[2.6,2.9)"> >> cxf-specs >> </feature> >> >> <feature version="[2.6,2.9)"> >> cxf-core >> </feature> >> >> <feature version="[2.6,2.9)"> >> cxf-jaxrs >> </feature> >> >> <feature version="[2.6,2.9)"> >> cxf-jaxws >> </feature> >> >> <feature version="[2.6,2.9)"> >> cxf-databinding-jaxb >> </feature> >> >> <feature version="[2.6,2.9)"> >> cxf-bindings-soap >> </feature> >> >> <bundle> >> mvn:org.apache.camel/camel-cxf-transport/2.11.4 >> </bundle> >> >> <bundle> >> mvn:org.apache.camel/camel-cxf/2.11.4 >> </bundle> >> </feature> >> Now, let's look at the 2.11.3 version: >> <feature name="camel-cxf" version="2.11.3" resolver="(obr)" >> start-level="50"> >> >> <feature version="2.11.3"> >> camel-spring >> </feature> >> >> <feature> >> jetty >> </feature> >> >> <feature version="[2.6,2.9)"> >> cxf >> </feature> >> >> <feature version="[2.6,2.9)"> >> cxf-specs >> </feature> >> >> <feature version="[2.6,2.9)"> >> cxf-core >> </feature> >> >> <feature version="[2.6,2.9)"> >> cxf-jaxrs >> </feature> >> >> <feature version="[2.6,2.9)"> >> cxf-jaxws >> </feature> >> >> <feature version="[2.6,2.9)"> >> cxf-databinding-jaxb >> </feature> >> >> <feature version="[2.6,2.9)"> >> cxf-bindings-soap >> </feature> >> >> <bundle> >> mvn:org.apache.camel/camel-cxf-transport/2.11.3 >> </bundle> >> >> <bundle> >> mvn:org.apache.camel/camel-cxf/2.11.3 >> </bundle> >> </feature> >> The only thing that has changed are the version numbers (from 2.11.3 >> -> 2.11.4). Now, for the maven folks, all we did was adjust the >> pom.xml file: >> >> - >> <cxf-version> >> 2.7.8 >> </cxf-version> >> + >> <cxf-version> >> 2.7.10 >> </cxf-version> >> I would assume this is okay. Am I missing something? >> >> >> On Mon, Feb 17, 2014 at 6:11 AM, Babak Vahdat >> < > >> babak.vahdat@ > >> > wrote: >>> Hi James, >>> >>> Even if we would mark the issue as not fixed, the behaviour divergency by >>> this release candidate @ the staging repo would be still there, that's: >>> For the non-OSGi folks who make use of camel-cxf Camel component, we >>> would >>> put CXF 2.7.10 for them into the classpath but for the OSGi folks who use >>> the camel-cxf Karaf feature, we would NOT allow them to make use of CXF >>> 2.7.10! >>> >>> Babak >>> >>> >>> James Carman wrote >>>> Why not just mark the issue as not fixed and release? Is the issue a >>>> show-stopper? >>>> >>>> On Sunday, February 16, 2014, Babak Vahdat < >>> >>>> babak.vahdat@ >>> >>>> > >>>> wrote: >>>> >>>>> -1 >>>>> >>>>> See >>>>> >>>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html >>>>> >>>>> Babak >>>>> >>>>> >>>>> hadrian wrote >>>>> > This is a vote to release Apache Camel 2.11.4, a patch release coming >>>>> > with about 26 issues fixed. >>>>> > >>>>> > Release notes: >>>>> > >>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645 >>>>> > >>>>> > >>>>> > Staging repo: >>>>> > >>>>> https://repository.apache.org/content/repositories/orgapachecamel-1003/ >>>>> > >>>>> > Tarballs: >>>>> > >>>>> https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/ >>>>> > >>>>> > >>>>> > Tag: >>>>> > >>>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d >>>>> > >>>>> > Please test this release candidate and cast your vote. >>>>> > [ ] +1 Release the binary as Apache Camel 2.11.4 >>>>> > [ ] -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-11-4-tp5747362p5747376.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-11-4-tp5747362p5747423.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-11-4-tp5747362p5747430.html > Sent from the Camel Development mailing list archive at Nabble.com.
