+1 for the last Camel 2.9.x release.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com
If you click at [1] from [2], the displayed page is empty. It's the same
for all other blog links.
We had the same issue in the past and Dan fixed it manually. I think there
is an issue in the Confluence WIKI exporter classes at [3].
It would be great if somebody could have a look at it soon. I ra
> Christian:
> +1
> I could install all features in Karaf 2.2.10 (with Java 6 ;-) ).
Works fine for my tests as well.
If nobody raise any issue against the release, I'll perform it tomorrow.
Cheers.
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Agree. Let's shoot for next week, end of this month.
Hadrian
On 04/22/2013 07:03 AM, Christian Müller wrote:
+1 for releasing it shortly.
Sent from a mobile device
Am 22.04.2013 09:36 schrieb "Claus Ibsen" :
Hi
When 2.11.0 is GA, we should IMHO do a last 2.9.x release, and then
retire that b
The Apache Camel project [1] is a powerful open source integration
framework based on known Enterprise Integration Patterns [2].
The Camel community announces the immediate availability of a new minor
release camel-2.11.0. This release is issued after 9 months of intense
efforts. During this perio
Seems like I was too quick to pull the trigger on that one. I wasn't
defining any log4j configuration in my test case and this cause the debug to
be turned on, but not outputted. The SLF4J debug method takes an Object and
not a String for its argument, so toString() will not be called when
evalua
Hi,
While working on a new Camel component
(https://issues.apache.org/jira/browse/CAMEL-5828) and doing a speed
comparison between SEDA and DISRUPTOR endpoints, we ran into a test that
would take a lot more time then expected. This test was about using a SEDA
endpoint with a lot of parameters d
Sorry, I forgot to commit my local change. It should be OK now.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.
Hi
I tried to merge this commit from trunk:
davsclaus:(svn)camel-2.11[camel-2.11.x:1470562]/$ svnmerge.py merge -r 1470508
svnmerge: no integration info available
On Mon, Apr 22, 2013 at 4:48 PM, Willem jiang wrote:
> Hi Claus,
>
> It should be OK now.
>
> --
> Willem Jiang
>
> Red Hat, Inc.
I would move to git first. Branching is also easier, imho.
$0.02,
Hadrian
On 04/22/2013 03:30 AM, Claus Ibsen wrote:
Hi
We should setup a branch for 2.11
https://svn.apache.org/repos/asf/camel/branches/
And I think in the process there is something to setup for svnmerge to
have that working a
Hi Claus,
It should be OK now.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (
Hi Willem
This is great. Let us know when the svnmerge has been setup, and ready to use.
On Mon, Apr 22, 2013 at 3:29 PM, Willem jiang wrote:
> There is a doc[1] in the CXF website.
> I'm work on setup the branch of camel-2.11.x now and will add a new doc to
> the camel.apache.org.
>
> [1]http
Hi
We already had this topic last year (for the 2.10.x branch) and for that
Willem already added the required steps for setting up such a branch:
http://camel.apache.org/release-guide.html#ReleaseGuide-Createanewmaintenancebranch
And this was the thread about it:
http://camel.465427.n5.nabble.c
There is a doc[1] in the CXF website.
I'm work on setup the branch of camel-2.11.x now and will add a new doc to the
camel.apache.org.
[1]http://cxf.apache.org/release-management.html
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www
Sorry, I just committed the fix.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (
+1 for releasing it shortly.
Sent from a mobile device
Am 22.04.2013 09:36 schrieb "Claus Ibsen" :
> Hi
>
> When 2.11.0 is GA, we should IMHO do a last 2.9.x release, and then
> retire that branch.
> Though 2.9.6 was released in early March. So when would be a good time
> to do that last 2.9.7 re
+1!!!
Sent from a mobile device
Am 22.04.2013 09:31 schrieb "Claus Ibsen" :
> Hi
>
> We should setup a branch for 2.11
> https://svn.apache.org/repos/asf/camel/branches/
>
> And I think in the process there is something to setup for svnmerge to
> have that working as well?
> I am not sure how tha
Hi Willem
Does this commit break the unit test in camel-jetty for you?
We have this NPE on trunk now. And it looks like its related to
getHttpConnectionManager.
Can you take a look?
Running org.apache.camel.component.jetty.MultiThreadedHttpGetTest
Tests run: 3, Failures: 0, Errors: 1, Skipped
Hi
When 2.11.0 is GA, we should IMHO do a last 2.9.x release, and then
retire that branch.
Though 2.9.6 was released in early March. So when would be a good time
to do that last 2.9.7 release? Should we wait a bit till eg june, or
should we release it sooner?
Its just that if we got trunk, 2.11,
Hi
We should setup a branch for 2.11
https://svn.apache.org/repos/asf/camel/branches/
And I think in the process there is something to setup for svnmerge to
have that working as well?
I am not sure how that is actually done.
Do we have some notes about this, and if not, we should IMHO add that,
20 matches
Mail list logo
