L.S.,
Over at the ServiceMix project, we are finalizing things for doing a
ServiceMix 4.4.0 release. The original plan was to use CXF 2.4.2 and Camel
2.8.1 because of an issue with the CXF 2.4.3 release in combination with
Felix. However, Dan has volunteered to do a quick CXF 2.4.4 release to
I can help to do the release of camel 2.8.3 :)
On Fri Oct 28 16:23:01 2011, Gert Vanthienen wrote:
L.S.,
Over at the ServiceMix project, we are finalizing things for doing a
ServiceMix 4.4.0 release. The original plan was to use CXF 2.4.2 and Camel
2.8.1 because of an issue with the CXF
AtomUtils.parseDocument() should be set with right TCCL
---
Key: CAMEL-4592
URL: https://issues.apache.org/jira/browse/CAMEL-4592
Project: Camel
Issue Type: Improvement
Upgrade abdera version to 1.1.3
Key: CAMEL-4593
URL: https://issues.apache.org/jira/browse/CAMEL-4593
Project: Camel
Issue Type: Task
Reporter: Willem Jiang
There are bunch fixes of
[
https://issues.apache.org/jira/browse/CAMEL-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang reassigned CAMEL-4593:
---
Assignee: Willem Jiang
Upgrade abdera version to 1.1.3
[
https://issues.apache.org/jira/browse/CAMEL-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-4592.
-
Resolution: Fixed
applied patch into trunk and 2.8.x branch.
L.S.,
That's awesome - thanks a lot!
Regards,
Gert Vanthienen
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Fri, Oct 28, 2011 at 10:46 AM, Willem Jiang willem.ji...@gmail.comwrote:
I can help to do the release of camel 2.8.3 :)
Hi Gert,
+1 for a new Camel 2.8.3 release.
I would propose to remove the repository/ tag for CXF.
It doesn't make sense to use a version range for the CXF feature, but
still specify a CXF version in the repository/ tag.
I would prefer to document for the users that they have to install the
Jean-Baptiste,
Removing the repository/ would avoid the issue, but it would also cause
the Camel descriptor to no longer be self-contained, so people would need to
read the documentation in order to get things working. One of the proposals
in the karaf-dev thread I referred to earlier, is to
The Apache Jenkins build system has built Camel (build #1364)
Status: Failure
Check console output at https://builds.apache.org/job/Camel/1364/ to view the
results.
Agree,
I'm raising the Karaf Jira (if it's not already done) and I'm gonna work
on it.
Regards
JB
On 10/28/2011 11:51 AM, Gert Vanthienen wrote:
Jean-Baptiste,
Removing therepository/ would avoid the issue, but it would also cause
the Camel descriptor to no longer be self-contained, so
Using Saxon to do XML split and xpath evaluation causes XPathExpression
exception
-
Key: CAMEL-4594
URL: https://issues.apache.org/jira/browse/CAMEL-4594
Project: Camel
Ok, than here is my -1 for this release
[
https://issues.apache.org/jira/browse/CAMEL-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13138328#comment-13138328
]
metatech commented on CAMEL-3401:
-
The line to add is the following :
bean
[
https://issues.apache.org/jira/browse/CAMEL-4594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4594.
Resolution: Fixed
Fix Version/s: 2.9.0
2.8.3
Using Saxon to do XML
[
https://issues.apache.org/jira/browse/CAMEL-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Babo updated CAMEL-4256:
--
Attachment: CAMEL-4256-2.patch
Submitting a patch which provides an implementation of
16 matches
Mail list logo