[
https://issues.apache.org/activemq/browse/CAMEL-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62489#action_62489
]
Claus Ibsen commented on CAMEL-3178:
Great I have added you to the project.
Db4o
[
https://issues.apache.org/activemq/browse/CAMEL-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62490#action_62490
]
Claus Ibsen commented on CAMEL-2331:
Async http client has WebDAV support
[
https://issues.apache.org/activemq/browse/CAMEL-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-2337.
Resolution: Fixed
Fix Version/s: (was: Future)
2.5.0
Upgrade
[
https://issues.apache.org/activemq/browse/CAMEL-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-3135:
---
Fix Version/s: (was: Future)
3.0.0
Option on route to specify that JMX
[
https://issues.apache.org/activemq/browse/CAMEL-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-2939:
---
Fix Version/s: (was: Future)
3.0.0
Cassandra component for Camel
Hi
Let's assume that we will synchronize releases of camel-extra with
camel-apache. Is it possible in such case to host camel-extra modules
on Maven public repo (just like camel-apache)?
I understand that we need to host codebase on Google code due to the
*GPL licensing problems. But as far as I
[
https://issues.apache.org/activemq/browse/CAMEL-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62491#action_62491
]
Gert Vanthienen edited comment on CAMEL-463 at 10/11/10 7:17 AM:
I've just commit fix to unstable db4o dependencies.
rev304 adds directory /maven2/others . This is repository for 3rd
party jars (like stable db4o) for camel-extra.
I also deployed com.db4o:db4o-core-java5:3.12 there.
rev305 (sorry for SVN comment missed) fixes db4o dependency to the
stable one
Hi
Yeah I think its great work. Makes it easier when we add other
projects to camel-extra and in need of a maven repo for its jars.
And you are welcome to work on a proper release of camel-extra when
Apache Camel 2.5 has been released.
It would be great to have them in sync as you wrote in
Sure, I'll handle it.
On Mon, Oct 11, 2010 at 2:47 PM, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
Yeah I think its great work. Makes it easier when we add other
projects to camel-extra and in need of a maven repo for its jars.
And you are welcome to work on a proper release of camel-extra
In theory it should be possible. Let me take it with the maven guys who
maintain maven central, and get back to you.
Cheers,
Hadrian
On Oct 11, 2010, at 4:36 AM, Henryk Konsek wrote:
Hi
Let's assume that we will synchronize releases of camel-extra with
camel-apache. Is it possible in such
[
https://issues.apache.org/activemq/browse/CAMEL-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-3206.
-
Resolution: Fixed
Just committed the patch into trunk.
Upgrade CXF version to 2.2.11
ScheduledPollConsumer should avoid runnable thread to die to ensure its kept
being scheduled
Key: CAMEL-3216
URL: https://issues.apache.org/activemq/browse/CAMEL-3216
[
https://issues.apache.org/activemq/browse/CAMEL-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-3216.
Resolution: Fixed
trunk: 1021396.
ScheduledPollConsumer should avoid runnable thread to die
AMQP Osgi Test.
---
Key: CAMEL-3217
URL: https://issues.apache.org/activemq/browse/CAMEL-3217
Project: Apache Camel
Issue Type: Test
Components: tests
Reporter: Johan Edstrom
Priority: Trivial
Deprecated Smooks component from Camel-Extra defines dependencies to
Smooks 1.0.1 jars. The problem is that the oldest version of Smooks
available on ibiblio is 1.1 [1]. The only public repository where I
can find 1.0.1 jars (according to the Google and findjar.com [2]) is
Maven 1 ibiblio mirror
Is there any sense in maintenance of camel-extra wiki [1] pages? Note
that we host camel-extra components documentation together with
camel-apache [2].
Maybe we should think about merging the camel-extra wiki with
camel-apache documentation? What do you think about migrating
camel-extra wiki to
http response as object
---
Key: CAMEL-3218
URL: https://issues.apache.org/activemq/browse/CAMEL-3218
Project: Apache Camel
Issue Type: Improvement
Components: camel-http
Affects Versions: 2.4.0
I think there is. The apache camel wiki is part of the camel distro. Unless we
create a separate area that will be clearly identified as camel-extra related
and won't end up in the book-in-one-page.
Hadrian
On Oct 11, 2010, at 3:22 PM, Henryk Konsek wrote:
Is there any sense in maintenance
[
https://issues.apache.org/activemq/browse/CAMEL-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62502#action_62502
]
Johan Edstrom commented on CAMEL-3209:
--
An idea for a patch is here.
The Smooks framework itself will integrate with Camel in their next release
http://blog.smooks.org/2010/09/23/smooks-camel-integration-revisited/
I think we should simply remove the camel-smooks at camel-extra as its
not used and to be replaced with the native support from Smooks
itself.
On
Hi
We have upgraded to Scalate 1.3 and CXF 2.2.11. We should be all set
in terms of dependencies.
Hadrian do you have time to do the 2.5 release?
It would be great to get it out really soon. Its been 3 months since
the last release and we have a lot of tickets resolved in this
release.
--
[
https://issues.apache.org/activemq/browse/CAMEL-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62510#action_62510
]
Claus Ibsen commented on CAMEL-3209:
Ah great nice you are helping out. Be careful though
[
https://issues.apache.org/activemq/browse/CAMEL-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62511#action_62511
]
Claus Ibsen commented on CAMEL-3218:
See nabble
Bindy should not trim separate in case end users use tab separators or the likes
Key: CAMEL-3219
URL: https://issues.apache.org/activemq/browse/CAMEL-3219
Project:
Thanks!
That was exactly what I wanted.
New patch coming tomorrow.
On Oct 11, 2010, at 11:20 PM, Claus Ibsen (JIRA) wrote:
[
https://issues.apache.org/activemq/browse/CAMEL-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62510#action_62510
]
[
https://issues.apache.org/activemq/browse/CAMEL-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62512#action_62512
]
Johan Edstrom commented on CAMEL-3209:
--
Well, the first I can live with if you want me.
[
https://issues.apache.org/activemq/browse/CAMEL-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-3219.
Resolution: Fixed
trunk: 1021635.
Bindy should not trim separate in case end users use tab
28 matches
Mail list logo