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.
