Hi Christian
I'm not aware of any better option other than raising a JIRA ticket by
INFRA.
Or maybe some other projects have already raised some as a lot of builds on
CI-Servers are in error.
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/many-Apache-Camel-build-tp5715
Because ubuntu1, ubuntu2, ubuntu4 and ubuntu5 are down, many of the Apache
Camel build failed, e.g. this one [1].
Is there something we can/should do to solve this?
[1]
https://builds.apache.org/view/A-F/view/Camel/job/Camel.2.9.x.fulltest/107/console
Thanks in advance,
Christian
Also, are we paying attention to pool reusage in a container?
Another dumb question ;)
On Jul 9, 2012, at 21:53, Scott England-Sullivan wrote:
> Christian,
>
> I am looking into creating a new Apache Commons project for the messaging.
> As information becomes available I will let you know.
>
I'd be +1 for the offline, branching and commit simplicity as well as a easier
merge.
On Jul 9, 2012, at 22:35, Daniel Kulp wrote:
> On Monday, July 09, 2012 09:48:32 PM Christian Müller wrote:
>> I would like to get your opinion about switching from SVN to Git [1].
>> At this point Git suppor
I added a new Jenkins build for the camel-2.10.x release branch [1] and
disabled the camel-2.8.x release branch, because this branch is now not
active supported. We may only want to make a Camel 2.8.7 release if there
is a security vulnerability with the last release version...
[1] https://builds.
Is there any reason for not using commons pool then?
Just a stupid question.
On Jul 9, 2012, at 21:53, Scott England-Sullivan wrote:
> Christian,
>
> I am looking into creating a new Apache Commons project for the messaging.
> As information becomes available I will let you know.
>
> On Thu,
The Apache Jenkins build system has built Camel.trunk.notest (build
#$BUILD_NUMBER)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1588/
to view the results.
On Monday, July 09, 2012 09:48:32 PM Christian Müller wrote:
> I would like to get your opinion about switching from SVN to Git [1].
> At this point Git support is pretty stable. All projects that's requested
> to be transferred has been switched so far.
>
> What's your preference?
> Should we "fo
Thanks Willem of taking care of it.
If you could send me the instructions for doing it, I would like to add it
to the release guide page [1].
[1] http://camel.apache.org/release-guide.html
Best,
Christian
On Mon, Jul 9, 2012 at 10:50 AM, Willem Jiang wrote:
> Hi Christian,
>
> I just setup a br
Christian,
I am looking into creating a new Apache Commons project for the messaging.
As information becomes available I will let you know.
On Thu, Jul 5, 2012 at 6:29 PM, Scott England-Sullivan
wrote:
> Hi Christian,
>
> I noticed after the fact that this was stated as a goal in the Camel
> ro
I would like to get your opinion about switching from SVN to Git [1].
At this point Git support is pretty stable. All projects that's requested
to be transferred has been switched so far.
What's your preference?
Should we "force" the switch or wait until (at some time) may all projects
are switche
Sorry, I overlooked Ashwin's vote:
The vote passes with:
[6] +1 (cmueller, cibsen, ningjiang, cshneider, akarpe, janstey)
[1] +1 non-binding (bvahdat)
[0] -1
Thanks to all who voted.
I already synced the artifacts to Maven central.
I will announce the release officially and blog about it after i
The vote passes with:
[5] +1 (cmueller, cibsen, ningjiang, cshneider, janstey)
[1] +1 non-binding (bvahdat)
[0] -1
Thanks to all who voted.
I already synced the artifacts to Maven central.
I will announce the release officially and blog about it after it's synced
to the mirrors.
Best,
Christian
And the Prop changes being commited are as the following:
Propchange: camel/branches/camel-2.10.x/components/camel-http/
--
Merged /camel/trunk/components/camel-http:r1359226
And:
Propchange: camel/branches/camel-2.
Hi
While backporting some fixes to the 2.10.x branch I realized that the
commits of mine contain a svn prop-change for the path:
camel/branches/camel-2.10.x/components/camel-http/
on the SVN repo *although* I've got no local change for that directory on my
workspace! And this happens as I do:
+1
On Thu, Jul 5, 2012 at 5:37 PM, Christian Müller <
christian.muel...@gmail.com> wrote:
> A new release candidate apache-camel-2.8.6 final is out with approximately
> 31 issues resolved so far: improvements and bug fixes [1].
>
> Please find the staging repo here:
> https://repository.apache.or
Hi Christian,
I just setup a branch 2.10.x and updated the 2.9.x to merge the change
from 2.10.x fix branch.
On Sun Jul 8 18:15:20 2012, Christian Müller wrote:
Could somebody of the core committers create a new camel-2.10.x release
branch and set/adjust the svn properties accordingly so tha
+1
-
-
Ashwin Karpe
Apache Camel Committer & Sr Principal Consultant
FUSESource (a Progress Software Corporation subsidiary)
http://fusesource.com
Blog: http://opensourceknowledge.blogspot.com
--
Hi,
I'm looking to implement some tests cases to test Cross Origin Resource
Sharing (CORS) with camel-websocket. Until now, we have used the lib Async
HTTP of the ning project (https://github.com/sonatype/async-http-client) to
design our client tests cases. Unfortunately, the existing code does no
19 matches
Mail list logo
