are settled.
I ran a complete unit test on my local laptop before commiting the changes.
There is a few TODO in the code, which I will work on as well, so
expect a few more commits. The TODO is minor/cosmetic changes I have
spotted, that can be improved.
--
Claus Ibsen
And then many of the things they need is installed out of the box.
I just wonder how widespread the usage of the commons-dbcp is out there?
And if anyone uses any alternatives? For example I dont recall I have
seen anyone use eg c3po in production.
--
Claus Ibsen
-
FuseSource
keep enjoy using Camel.
Am 12.08.2011 17:29, schrieb Claus Ibsen:
Hi
Recently the ExecutorServiceStrategy had a bigger refactor
(https://issues.apache.org/jira/browse/CAMEL-4244)
Such as renaming the class to a better name ExecutorServiceManager.
Also introducing a ThreadPoolFactory
the
executorServiceRef).
So in Java DSL you can do
ThreadPoolProfile myProfile = ...
.threads(myProfile)
Will this help Christian?
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel
the product description
updated a bit to reflect where we are today with Apache Camel?
For example we may want to mention Apache Karaf on the front page as a
product that Camel runs with out of the box. etc.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http
issue JIRA page.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
is to be dropped.
Any thoughts?
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
ticket as well.
--
View this message in context:
http://camel.465427.n5.nabble.com/SFTP-via-proxy-not-possible-tp4706296p4706296.html
Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http
approach
On 14 Aug 2011, at 10:35, Claus Ibsen wrote:
Hi
I wonder if we should consider dropping any official support for Maven
2.x on the Apache Camel project?
I guess most people is now migrated to Maven 3.0. And the last number
of releases has been done using Maven 3.0.x.
Also in light
out put
and store it on local please share it..
Thanks in advance
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-http-sample-program-tp4706867p4706867.html
Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibsen
Hi
I have polished the readme.txt file in the source code to be similar
to the text on the public Apache Camel website
http://camel.apache.org/
On Sat, Aug 13, 2011 at 1:14 PM, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
I noticed the README.txt file in the distribution kit starts as follows
.nabble.com/Camel-Apache-in-Jboss-tp4707916p4707916.html
Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author
=truemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.smack/${smack-bundle-version}/bundle
bundle
dependency=truemvn:org.springframework/spring-jms/${spring-version}/bundle
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
--
View this message in context:
http://camel.465427.n5.nabble.com/Chmod-files-after-upload-via-sftp-tp4711276p4711276.html
Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http
for Camel 2.x that is 2+ years old, and for a
feature that has been in there for 18+ months.
We have Camel 3.0 where the API can be more open for changes.
Christian
Am 12.08.2011 17:29, schrieb Claus Ibsen:
Hi
Recently the ExecutorServiceStrategy had a bigger refactor
(https
On Thu, Aug 18, 2011 at 1:50 PM, Claus Ibsen claus.ib...@gmail.com wrote:
On Thu, Aug 18, 2011 at 1:25 PM, Christian Schneider
ch...@die-schneider.net wrote:
Hi Claus,
I just saw that you also changed the ThreadPoolFactory interface to not use
the profiles and instead have several methods
On Thu, Aug 18, 2011 at 2:07 PM, Christian Schneider
ch...@die-schneider.net wrote:
Am 18.08.2011 13:50, schrieb Claus Ibsen:
On Thu, Aug 18, 2011 at 1:25 PM, Christian Schneider
ch...@die-schneider.net wrote:
Hi Claus,
I just saw that you also changed the ThreadPoolFactory interface
On Thu, Aug 18, 2011 at 2:07 PM, Christian Schneider
ch...@die-schneider.net wrote:
Am 18.08.2011 13:50, schrieb Claus Ibsen:
On Thu, Aug 18, 2011 at 1:25 PM, Christian Schneider
ch...@die-schneider.net wrote:
Hi Claus,
I just saw that you also changed the ThreadPoolFactory interface
professionalism)
- ThreadPoolProfile as you override clone() you could consider
implementing Cloneable interface as well
- The parameter name for addDefaults could imho be improved to be
other instead of defaultProfile2 which seems a bit odd name
Also the javadoc parameter is not described
--
Claus Ibsen
19.08.2011 10:00, schrieb Claus Ibsen:
The latest commits look good.
Only a few cosmetic changes that would be nice to do
- Add missing/fix javadoc to ExecutorServiceManager (its a SPI
interface so full javadoc shows professionalism)
- Add missing/fix javadoc to ThreadPoolFactory (its a SPI
://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel
of this code that components can
depend on. The smaller the better.
Currently any change in camel-core could break any component. If we had a
proper API then only API changes could break the components.
Am 19.08.2011 15:59, schrieb Claus Ibsen:
I wonder if the impl package had been named core
package as
Main as ServiceSupport will be needed by many other classes.
Christian
Am 19.08.2011 16:43, schrieb Claus Ibsen:
I am not sure moving Main to a main package is a good idea.
As you would lock yourself into only having the Main class there.
What about adding
--
svn:keywords = Rev Date
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
but that will
probably create too much incompatibility.
Christian
Am 24.08.2011 14:13, schrieb Claus Ibsen:
On Tue, Aug 23, 2011 at 12:38 PM, Christian Schneider
ch...@die-schneider.net wrote:
I wonder what our scope for the org.apache.camel.spi package is vs the
org.apache.camel (API) package.
I know
.
Putting them in org.apache.camel.api seems a bit weird, as they would
be the only pieces in there.
And for Camel 2.x we should keep the API stable and not move around
stuff all the time.
Christian
Am 24.08.2011 17:53, schrieb Claus Ibsen:
On Wed, Aug 24, 2011 at 3:04 PM, Christian Schneider
ch
would be 2.8.1
release.
Any feedback?
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
can be easily backported.
I will update ServiceMix to include Camel 2.8.1.
Regards
JB
On 08/25/2011 09:58 AM, Claus Ibsen wrote:
Hi
Its been 1 month since Camel 2.8.0 was released.
And we have a 2.8 branch where we have merged bug fixes.
I suggest that we consider doing a 2.8.1
in api.management.events.
Christian
Am 24.08.2011 19:12, schrieb Claus Ibsen:
On Wed, Aug 24, 2011 at 6:17 PM, Christian Schneider
ch...@die-schneider.net wrote:
Hi Claus,
we can do that but then we have to move the impl classes somewhere
else. We
may not mix impl and api in the same
in a separate package already
the does not depend on the management impl I did not move them but they
would be better placed in api.management.events.
Christian
Am 24.08.2011 19:12, schrieb Claus Ibsen:
On Wed, Aug 24, 2011 at 6:17 PM, Christian Schneider
ch...@die-schneider.net wrote:
Hi
On Thu, Aug 25, 2011 at 10:17 AM, Claus Ibsen claus.ib...@gmail.com wrote:
On Thu, Aug 25, 2011 at 9:40 AM, Christian Schneider
ch...@die-schneider.net wrote:
I have another proposal that could work better and is quite near to what we
have.
org.apache.camel.management.api
We could consider
(cool);
from(direct:start).enrichRef(cool, agg);
}
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http
Hi
There is a fair number of checkstyle issues on trunk on camel-core. I
suspect its due some of the latest refactorings.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author
maven reporting web tooling
being able to display them.
However its just much easier to run the cmd from the command line once
in a while.
Christian
Am 27.08.2011 18:29, schrieb Claus Ibsen:
Hi
There is a fair number of checkstyle issues on trunk on camel-core. I
suspect its due some
.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
party tooling can use the grammar file to generate a
parser for its tooling.
Am 29.08.2011 10:18, schrieb Claus Ibsen:
Hi
The current Simple language in camel-core has reached its potential in
terms of maintenance and how easy it would be, for example to add new
functions and operators
On Mon, Aug 29, 2011 at 10:18 AM, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
The current Simple language in camel-core has reached its potential in
terms of maintenance and how easy it would be, for example to add new
functions and operators. Likewise the current error reporting
use if you want a
more powerful language.
For example camel-groovy, or use camel-script so you can use JavaScript etc.
All these languages have support by IDEs
On 8/29/11 8:19 PM, Claus Ibsen wrote:
On Mon, Aug 29, 2011 at 11:14 AM, Christian Schneider
ch...@die-schneider.net wrote:
Hi Claus
and what it does.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
in the org.apache.camel.util.stream package
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
/camel-cxf/src/test/resources/org/apache/camel/component/cxf/spring/testEndpoint.properties
--
svn:mime-type = text/plain
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http
=project+%3D+CAMEL+AND+issuetype+%3D+Bug+AND+resolution+%3D+Fixed+AND+fixVersion+%3D+12316374+AND+status+%3D+Resolved+ORDER+BY+updated+DESC%2C+key+DESC
There is 37 bugs fixed, and there may be some fixes which havent been
backported.
--
Claus Ibsen
-
FuseSource
Email: cib
this before? And know a reason for doing this.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Maybe we need to add this profile in camel-core
http://maven.apache.org/general.html#tools-jar-dependency
Also discussed here
http://jenkins.361315.n4.nabble.com/com-sun-tools-jar-1-5-is-missing-td390964.html
On Tue, Aug 30, 2011 at 11:49 AM, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
@deprecated in favor of some other class etc.
Our user base should have this information up-front so they can take
that into account, in their migration plans.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog
--
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http
loaded and
whatnot. That was a pain in the past.
Christian
Am 31.08.2011 17:43, schrieb Claus Ibsen:
On Wed, Aug 31, 2011 at 5:40 PM, Christian Schneider
ch...@die-schneider.net wrote:
Hi all,
can someone tell me what the purpose of camel-core-xml is and why it has
to
be a spearate
reintegrating
camel-core-xml would reduce the number of jars again which is good.
That is still to be decided. And to be discussed later when Camel 3.0
is starting to take form.
Christian
Am 31.08.2011 17:54, schrieb Claus Ibsen:
On Wed, Aug 31, 2011 at 5:51 PM, Christian Schneider
ch
Talend Application Integration Division http://www.talend.com
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
();
- assertEquals(cheese, uri);
+ assertEquals(bean:cheese, uri);
Producer producer = pe.createProducer();
Exchange exchange = producer.createExchange();
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
On Wed, Aug 31, 2011 at 10:15 PM, Donald Whytock dwhyt...@gmail.com wrote:
On Wed, Aug 31, 2011 at 3:26 PM, Claus Ibsen claus.ib...@gmail.com wrote:
The core is 1.6mb which is not bloated. In fact with the core you can
do really a lot with Camel, which impress
a lot of people, and help make
the user account on the confluence yourself.
Then tell us your userid and we can then give you karma.
Thanks!
Mathieu
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author
if you need more info.
This is great. I can see the ICLA as well.
Hi you need to create the user account on the confluence yourself.
Then tell us your userid and we can then give you karma.
Thanks!
Mathieu
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
());
assertEquals(timeout, e.getTimeout());
assertEquals(outFile, e.getOutFile());
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http
an easy start but logically the parts of camel-core need to be nicely
separated.
Christian
Am 31.08.2011 21:26, schrieb Claus Ibsen:
On Wed, Aug 31, 2011 at 7:45 PM, Christian Schneider
ch...@die-schneider.net wrote:
The camel-core is already bloated anyway. I see no reason
if possible, lets take the opportunity and get
the RC cut so we could get a release our the door
for the benefit for our sister projects at Apache.
On 08/30/2011 05:44 AM, Claus Ibsen wrote:
Anyone got cycles to take a look at the bug fixes in Camel 2.9, which
may not have been backported
. I would like Camel 2.8.1 as part of
the new SMX 4.4 release.
There is not so often a new SMX release so we should put in the best
Camel version we can do.
Regards
JB
On 09/02/2011 10:00 AM, Claus Ibsen wrote:
On Tue, Aug 30, 2011 at 3:29 PM, Hadrian Zbarceahzbar...@gmail.com
wrote:
I
On Fri, Sep 2, 2011 at 11:18 AM, Claus Ibsen claus.ib...@gmail.com wrote:
On Fri, Sep 2, 2011 at 10:11 AM, Jean-Baptiste Onofré j...@nanthrax.net
wrote:
Hi guys,
I would like to release SMX 4.4 soon. For now, the target is Camel 2.8.0. We
still have some time in SMX to update to Camel 2.8.1
On 09/02/2011 01:59 AM, Claus Ibsen wrote:
This seems over reacting.
Can you post on @dev why you suddenly change all the working unit
tests like this?
Camel end users have been using these components without problems, and
they are easier to use without having to do URL encoding!
On Fri
@6a8c436b
with 0 in cache and 1 misses
eg I can see that when Camel is shutdown this type converter is as
well, where I then would be able to clear the caches.
And thus not leak resources.
On 08/31/2011 03:55 PM, Claus Ibsen wrote:
I wonder if there wont be a problem when you shutdown camel
() throws Exception {
+ // noop
+ }
+
+ public void stop() throws Exception {
+ // clear caches so we dont leak
+ cache.clear();
+ misses.clear();
+ }
+
}
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http
do you want to do instead? Introduce a clear() or reset() method,
and then need to invoke that from the
type converter registry.
You need to do something to ensure the caches is cleared, so we dont leak.
Using service is the preferred way in Camel.
On Fri, Sep 2, 2011 at 5:02 PM, Claus Ibsen
On 09/02/2011 08:32 AM, Claus Ibsen wrote:
On Fri, Sep 2, 2011 at 2:20 PM, Hadrian Zbarceahzbar...@gmail.com
wrote:
Not sure I understand your request, please clarify.
Can you post on @dev what you see as problems with the endpoint uris.
You create a number of tickets and mark
.
So it would be a matter of time before the prototype is ready as a
donation to Apache and to be included in Camel 2.9.
the prototype is located here
https://github.com/davsclaus/camel-simple2
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
.
Christian
--
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http
project).
From community point of view. Keep the API stable in our old and
beloved Camel 2.x product.
From community point of view. Start a discussion about Camel 3.0, as
we think the Camel 2.x product is old and stable.
But the community would like a brand new Camel 3.0 in early 2012.
--
Claus
is settled a bit and takes form, then we could look at the
gap from 3.0 to 2.x and put in migration guides, and possible some
@deprecations in the 2.x API. We should not do it the wrong way
around by experimenting with the 2.x API.
Hadrian
On Sep 5, 2011, at 10:04 AM, Claus Ibsen wrote:
Hi
I
, 2011, at 10:04 AM, Claus Ibsen wrote:
Hi
I am writing this mail with a community hat as well being a very
concerned Camel team member.
The API in camel-core had a fair number of changes recently, which is
a strong concern from a community point of view.
Basically the community views Camel 2
looking for
alternatives for Camel. I don't want this problem in the future.
Christian
Am 05.09.2011 16:04, schrieb Claus Ibsen:
Hi
I am writing this mail with a community hat as well being a very
concerned Camel team member.
The API in camel-core had a fair number of changes
with past versions, and also on a line by line bases see
who/when/commit logs what has been changed.
For example the class AsyncProcessorTypeConverter was moved in the
last commit. But the commit was a delete + add, which means all the
previous commit logs of that class is gone.
--
Claus Ibsen
:
http://camel.465427.n5.nabble.com/Problem-with-code-to-redirect-jetty-to-http4-tp4782847p4782847.html
Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
-tp4770632p4773307.html
Sent from the Camel Development mailing list archive at Nabble.com.
--
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
--
Claus Ibsen
-
FuseSource
=12317152
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
(CompilerMojo.java:128)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http
Christian Schneider:
Hi Claus,
I also could not reproduce the error. Will send the details of my work
machine later.
I guess the most probable cause should be the jdk version.
Christian
Am 11.09.2011 09:33, schrieb Claus Ibsen:
Hi
Apache Jenkins is reporting errors on Camel trunk
Okay the patch seems to work. Apache CI server can now compile and
test camel-core.
Its currently running a full test
https://builds.apache.org/job/Camel.trunk.fulltest.windows/15/console
On Mon, Sep 12, 2011 at 7:59 AM, Claus Ibsen claus.ib...@gmail.com wrote:
Thanks
I committed
.
Here's my +1
Hadrian
[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12317152
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author
maven-bundle-version2.3.5/maven-bundle-version
-openjpa-version1.2.2/openjpa-version
+openjpa-version2.1.1/openjpa-version
/properties
mailingLists
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
at: Thu Sep 15 10:44:17 CEST 2011
[INFO] Final Memory: 11M/30M
[INFO]
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http
available for
download from the Apache site [1].
[1] - http://camel.apache.org/download
[2] - http://camel.apache.org/camel-281-release.html
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http
,
This message acknowledges receipt of your ICLA, which has been filed in
the Apache Software Foundation records.
If you have been voted in as a committer, please advise the project PMC
that your ICLA has been filed.
Warm Regards,
Craig L Russell
Secretary, Apache Software Foundation
--
Claus
this, and cannot keep the documentation - source code in sync.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
the gap from 2.8.0, 2.8.1 to 2.8.2 is now very big. This is not desireable.
On Tue, Sep 20, 2011 at 8:11 AM, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
Dan what is the reason why you backport so many commits to 2.8.2 from 2.9?
The problem is that its a lot of new features, non trivial bug fixes
guess it may be a bug - it is a single encoder, but it doesnt work if
we use encoder command.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-netty-encode-bug-tp4825369p4825369.html
Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus
. it will set the pattern that others will follow. Its not that
we expect that you will break anything, but others might do by
accident.
On 21 Sep 2011, at 04:08, Daniel Kulp wrote:
On Tuesday, September 20, 2011 7:20:20 PM Claus Ibsen wrote:
Hi Dan
Do you care to discuss this?
You keep on backporting
not that
we expect that you will break anything, but others might do by
accident.
On 21 Sep 2011, at 04:08, Daniel Kulp wrote:
On Tuesday, September 20, 2011 7:20:20 PM Claus Ibsen wrote:
Hi Dan
Do you care to discuss this?
You keep on backporting non bug fixes, new features and whatnot
.
On 21 Sep 2011, at 04:08, Daniel Kulp wrote:
On Tuesday, September 20, 2011 7:20:20 PM Claus Ibsen wrote:
Hi Dan
Do you care to discuss this?
You keep on backporting non bug fixes, new features and whatnot.
People who run Camel in production and they may want to upgrade to
2.8.2
/camel/branches/camel-2.7.x
Repository Root: https://svn.apache.org/repos/asf
So when I run
svnmerge.py merge -r 1124595
It cannot merge that fix to the 2.7 branch.
I know some of you guys are svnmerge.py experts, and maybe can check it out.
--
Claus Ibsen
-
FuseSource
Email: cib
manually for you... not sure the best way to fix this up...
Thanks Jon.
Yeah that seems messed up. We should be looking into backport some of
the important issues we have found
recently which may also affect the 2.7 branch.
On Thu, Sep 22, 2011 at 9:29 AM, Claus Ibsen claus.ib...@gmail.com
are merging recent
bug fixes back to the 2.7 branch?
Dan
On Thu, Sep 22, 2011 at 9:29 AM, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
I am in need to backport CAMEL-3962 to the Camel 2.7 branch.
The commit has svn rev: 1124595
But when I check the svnmerge.py avail list
to find an older svnmerge.py file that dont fail at the end.
If anyone got a .py file working, then feel free to attach on a mail
and send to me, or this @dev.
On Thu, Sep 22, 2011 at 3:34 PM, Daniel Kulp dk...@apache.org wrote:
On Thursday, September 22, 2011 7:45:28 AM Claus Ibsen wrote
such as:
new components, and other improvements, new features, which we think
is worthwhile
and that the community would like to have in the Camel 2.9 release.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http
pieces, and have a
camel-api JAR (or whatever a good name could be )
which has the end user API. Then from Camel 3.0.0 onwards we have a
much better platform to keep a good and stable API for the
large and growing Camel community.
Christian
Am 23.09.2011 13:13, schrieb Claus Ibsen:
Hi
I
On Thu, Sep 22, 2011 at 7:02 PM, Daniel Kulp dk...@apache.org wrote:
On Thursday, September 22, 2011 6:44:42 PM Claus Ibsen wrote:
Hi
I gave the DoMerges tool a try and it worked fine.
However as my svnmerge.py python script causes some UTF-8 error after
the merge is done, the DoMerges
6:44:42 PM Claus Ibsen wrote:
Hi
I gave the DoMerges tool a try and it worked fine.
However as my svnmerge.py python script causes some UTF-8 error after
the merge is done, the DoMerges tool breaks
after one merge.
I tried downloading the latest svnerge.py file from
Also how to do it with the mentioned Java/Python scripts, as we have it done
with our release step-by-step guide. I didn't know these scripts and nobody
told me about their existence. I was not able to find a WIKI page about it
(with my mobile phone ;-) ). I could imagine, I'm not the only
in the release notes for that
given release.
3) Still not clear why we backport many issues to 2.8.2 and not to 2.7.4.
I stess this to make it clear for everybody, document it and to provide a
better mentoring for new committers.
Christian
Sent from a mobile device
--
Claus Ibsen
a
better mentoring for new committers.
Yes, by all means we should document that. It'll be helpful to both
committers and users at large who would know what to expect.
Christian
Sent from a mobile device
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http
the copy from Dan.
I had trouble today backporting a fix to the 2.7 branch.
Could anyone try to backport CAMEL-4487? The rev number in the 2.8
branch is: 1175323
CAMEL-4487 is a low-risk, minor bug fix, that would be safe to
backport to the 2.7 branch.
--
Claus Ibsen
-
FuseSource
801 - 900 of 12030 matches
Mail list logo
