Re: About Apache Mina2 dependency being upgraded to 2.0.5

2012-09-27 Thread Babak Vahdat
Am 28.09.12 07:57 schrieb "Claus Ibsen" unter : >Hi Babak > >Well spotted again. The camel-mina2 tests passed fine. So I guess the >issue is more related to 3rd party frameworks not compiled against >Mina 2.0.5, but using the older API in 2.0.x. such as the FTP >libraries and whatnot. Like the

Re: About Apache Mina2 dependency being upgraded to 2.0.5

2012-09-27 Thread Claus Ibsen
Hi Babak Well spotted again. The camel-mina2 tests passed fine. So I guess the issue is more related to 3rd party frameworks not compiled against Mina 2.0.5, but using the older API in 2.0.x. such as the FTP libraries and whatnot. But still its a critical issue for people as they cannot easily up

About Apache Mina2 dependency being upgraded to 2.0.5

2012-09-27 Thread Babak Vahdat
Hi, Today we upgraded Apache Mina2 dependency from 2.0.4 to 2.0.5 which is NOT binary compatible anymore because of the following revision (the IoAcceptor.bind() method with one argument has been replaced with varargs variant causing NoSuchMethodError @ runtime): http://svn.apache.org/viewvc?view

Re: [Patch] CAMEL-5643 Allow users to store body and arbitrary headers as text within a datasource

2012-09-27 Thread Christian Müller
Hello Alan! I'm a bit busy at present like others too. If you do not get an answer in short time, it doesn't mean there is something wrong. The issue is logged and your patch attached. I'm sure a committer will pick it up in the next days and may be come back with questions or commit your patch.

Re: SJMS Jenkins Failures

2012-09-27 Thread Christian Müller
No worries. Good to know you have an eye on it. Best, Christian Sent from a mobile device Am 27.09.2012 17:19 schrieb "Scott England-Sullivan" : > Hi All, > > I see that there are some timing issues with new SJMS batch transaction > unit tests I have added. I am reviewing and looking at solutio

Re: [camel-extra] Changed groupId and package name of camel-esper-demo

2012-09-27 Thread Henryk Konsek
> IMHO it should be the same for the entire camel-extra project. > And only the artifcatId should be changed for the various Maven modules. Sounds fine. We can stick to the same groupId as in other Camel-Extra modules. And name artifact camel-example-esper . > Also IMHO dont make the artifactId l

camel pull request: Update camel-core/src/main/java/org/apache/camel/manage...

2012-09-27 Thread grahamlittle
GitHub user grahamlittle opened a pull request: https://github.com/apache/camel/pull/5 Update camel-core/src/main/java/org/apache/camel/management/DefaultManag... ...ementAgent.java https://issues.apache.org/jira/browse/CAMEL-5127?page=com.atlassian.jira.plugin.system.issue

Re: [camel-extra] Changed groupId and package name of camel-esper-demo

2012-09-27 Thread Claus Ibsen
On Thu, Sep 27, 2012 at 9:06 AM, Henryk Konsek wrote: >> Why not call the package org.apachextras.camel.examples.esper > > I'm ok with that as long as we rename the groupId to > org.apache-extras.camel-extra.examples as well. What do you think > about it? > Why do you want to change the group id

Re: [camel-extra] Changed groupId and package name of camel-esper-demo

2012-09-27 Thread Christian Müller
groupId should be org.apache-extra.camel (as we have it in Apache Camel) or org.apache-extra.camel.examples artifactId should be camel-example-esper from my point of view. Best, Christian On Thu, Sep 27, 2012 at 9:06 AM, Henryk Konsek wrote: > > Why not call the package org.apachextras.camel.e

Re: [camel-extra] Changed groupId and package name of camel-esper-demo

2012-09-27 Thread Henryk Konsek
> Why not call the package org.apachextras.camel.examples.esper I'm ok with that as long as we rename the groupId to org.apache-extras.camel-extra.examples as well. What do you think about it? -- Henryk Konsek http://henryk-konsek.blogspot.com