Hi
Just an update. Hadrian has started the 2.6 release today.
So keep an eye when he announces the VOTE and the binaries so we can
give it a last minute test spin.
On Sun, Jan 23, 2011 at 4:15 PM, Claus Ibsen claus.ib...@gmail.com wrote:
Hi Hadrian
Can you keep us posted on the progress of
Hi Hadrian
Can you keep us posted on the progress of the release build?
We are holding up Apache ServiceMix 4.3.0 release as they wait for Camel 2.6.
So it would be great to get the release build and in vote asap.
On Sat, Jan 22, 2011 at 10:21 AM, Christian Schneider
ch...@die-schneider.net
to our build?
Christian
-Ursprüngliche Nachricht-
Von: Hadrian Zbarcea [mailto:hzbar...@gmail.com]
Gesendet: Freitag, 21. Januar 2011 16:57
An: dev@camel.apache.org
Betreff: Re: Preparing for Camel 2.6 release
I would like to have at least one clean build in hudson before the release.
Other
Hi Hadrian,
the latest build #130 was successful. I think we could be ready for a
release.
Christian
Am 21.01.2011 16:56, schrieb Hadrian Zbarcea:
I would like to have at least one clean build in hudson before the release.
Other than that we're good to go. Looks like the latest build
build?
Christian
-Ursprüngliche Nachricht-
Von: Hadrian Zbarcea [mailto:hzbar...@gmail.com]
Gesendet: Freitag, 21. Januar 2011 16:57
An: dev@camel.apache.org
Betreff: Re: Preparing for Camel 2.6 release
I would like to have at least one clean build in hudson before the
release
Hi
Okay Camel 2.6 seems good now. Just fixed a few tests failures
reported on CI servers, often due they are much slower than our local
fast laptops.
CXF 2.3.2 is about to hit the streets so we should be good to go.
So please refrain from committing to trunk, unless its a CI unit test fix :).
Hi
Dan Kulp have confirmed that CXF 2.3.2 has been voted and released.
I have just commited the updates to the camel trunk code to upgrade to
CXF 2.3.2.
We should be good to go for a release.
We have been testing with 2.3.2-SNAPSHOT for a week so the camel-cxf
should work well with the upgrade.
I would like to have at least one clean build in hudson before the release.
Other than that we're good to go. Looks like the latest build didn't go to well
[1]. I am looking into it. As soon as we have something green I'll start
building the release.
Hadrian
[1]
@camel.apache.org
Betreff: Re: Preparing for Camel 2.6 release
I would like to have at least one clean build in hudson before the release.
Other than that we're good to go. Looks like the latest build didn't go to well
[1]. I am looking into it. As soon as we have something green I'll start
building
On Fri, Jan 21, 2011 at 4:56 PM, Hadrian Zbarcea hzbar...@gmail.com wrote:
I would like to have at least one clean build in hudson before the release.
Other than that we're good to go. Looks like the latest build didn't go to
well [1]. I am looking into it. As soon as we have something green
On Fri, Jan 21, 2011 at 4:56 PM, Hadrian Zbarcea hzbar...@gmail.com wrote:
I would like to have at least one clean build in hudson before the release.
Other than that we're good to go. Looks like the latest build didn't go to
well [1]. I am looking into it. As soon as we have something green
Hi
I have created a ticket to upgrade to CXF 2.3.2
https://issues.apache.org/jira/browse/CAMEL-3553
The CXF vote is in progress
http://cxf.547215.n5.nabble.com/VOTE-Apache-CXF-2-3-2-td3345633.html
And the Camel source code trunk is testing against a 2.3.2-SNAPSHOT.
So we use that to catch any
Hi Aaron,
I think this solution could avoid adding the dependency of script API
into camel-core in Camel 2.x. +1 for it.
When we move to Camel 3.x, we could let the camel-core looking up the
ScriptEngineFacotries.
BTW, we are closing to Camel 2.6 release, if the patch can't catch up
the
Camel 2.6 is almost ready for a release. The last hudson test [1] only had 4
failures in camel-scala (looks like the problem wasn't fully resolved by
Willem, and the problem still exists in the current build [2]). It looks like
everything else is really stable and I'd suggest not committing
Hi Hadrian,
I'm gonna upgrade SMX projects to use CXF 2.3.2 and Camel 2.6-SNAPSHOT
to perform some tests and validate that unit tests are fine.
The plan is to release SMX 4.3.0 with:
- Karaf 2.1.3
- Camel 2.6.0
- CXF 2.3.2
- Spring 3.0.5.RELEASE
Regards
JB
On 01/17/2011 03:31 PM, Hadrian
On Monday 17 January 2011 9:31:33 am Hadrian Zbarcea wrote:
Camel 2.6 is almost ready for a release. The last hudson test [1] only had
4 failures in camel-scala (looks like the problem wasn't fully resolved by
Willem, and the problem still exists in the current build [2]). It looks
like
Anyway, as reminder, in ServiceMix, the Camel features descriptor is
overrided. So if you use CXF 2.3.1 in Camel 2.6, the Camel feature
descriptor embedded in ServiceMix will use CXF 2.3.2.
So even if you wait for CXF 2.3.2 or not, finally in ServiceMix, CXF
2.3.2 will be used :)
Regards
JB
On Mon, Jan 17, 2011 at 3:55 PM, Daniel Kulp dk...@apache.org wrote:
On Monday 17 January 2011 9:31:33 am Hadrian Zbarcea wrote:
Camel 2.6 is almost ready for a release. The last hudson test [1] only had
4 failures in camel-scala (looks like the problem wasn't fully resolved by
Willem, and the
On Monday 17 January 2011 10:01:32 am Claus Ibsen wrote:
On Mon, Jan 17, 2011 at 3:55 PM, Daniel Kulp dk...@apache.org wrote:
On Monday 17 January 2011 9:31:33 am Hadrian Zbarcea wrote:
Camel 2.6 is almost ready for a release. The last hudson test [1] only
had 4 failures in camel-scala
As discussed on IRC, ServiceMix should provide more unit tests,
especially around Camel and CXF used in OSGi.
First, I'm gonna update to Camel 2.6-SNAPSHOT and CXF 2.3-SNAPSHOT in
preparation of the upgrade. It should be ready tonight (GMT+1 time).
After that, I'm gonna work on it. If you need
Typing mistake:
If you see some areas that should be spotted in the unit tests, please
keep us posted.
I'm tired before starting the unit tests coding :)
Regards
JB
On 01/17/2011 04:37 PM, Jean-Baptiste Onofré wrote:
As discussed on IRC, ServiceMix should provide more unit tests,
especially
I reverted the changes for
https://issues.apache.org/jira/browse/CAMEL-3311and closed this issue.
I will implement this feature in a better solution in
Camel 2.7 with
https://issues.apache.org/jira/browse/CAMEL-3515https://issues.apache.org/jira/browse/CAMEL-3311
.
Thanks Christian
All tickets for Camel 2.6 has now been resolved. So lets give the CI
servers some time to test it.
If all is well early next week, then Hadrian can start cutting the release.
Thanks for all the hard work on this release. Its another staggering
250+ tickets resolve release.
And
Sorry for the delay on https://issues.apache.org/jira/browse/CAMEL-3311, but
I fixed it now. There was some more classes to update than I expected...
And https://issues.apache.org/jira/browse/CAMEL-3545 also has taken a few
hours to figure it out. Could some of you look into
On Sat, Jan 15, 2011 at 3:40 PM, Christian Müller
christian.muel...@gmail.com wrote:
Sorry for the delay on https://issues.apache.org/jira/browse/CAMEL-3311, but
I fixed it now. There was some more classes to update than I expected...
And https://issues.apache.org/jira/browse/CAMEL-3545 also
Hi
I have fixed CAMEL-3545. It now validates the method name in all 3
cases. Well spotted Christian.
See CAMEL-2920.
Its used to pre-check Camel routes on startup, that the bean and
method names are valid.
This help spot typos before the Camel application is started.
Previously it only worked
So right now, I have the Activator identifying and actually loading
ScriptEngineFactories, which is why there is the dependency on
javax.script.
For now (Camel 2.x) I can instead have the Activator just identify the
bundles with a script engine config file (META-INF/services/...) and
hand out
On Wed, Jan 12, 2011 at 11:15 PM, Christian Müller
christian.muel...@gmail.com wrote:
Claus, I will work on friday at CAMEL-3311.
Thats perfect. Would be lovely if we got all tickets fixed before monday.
Then the CI servers can run throughly tests over the weekend. And if
all is green, then
I would like to get https://issues.apache.org/jira/browse/CAMEL-3481
into the 2.6 release (make camel-script work in OSGi). I have a
solution available, but it adds a dependency to javax.script in
camel-core in the OSGi Activator (fine for Java 1.6, new dependency
for 1.5). Just want to make
Hi Aaron,
Camel 3.0 will move to JDK 1.6 officially I think we should have no
problem with that.
For the Camel 2.6, if we make the camel-core dependency of the script
api scope to be provided. It will not cause any trouble in most case, as
the Activator will never be used if we don't deploy
On 1/14/11 10:23 AM, Aaron Mulder wrote:
I would like to get https://issues.apache.org/jira/browse/CAMEL-3481
into the 2.6 release (make camel-script work in OSGi). I have a
solution available, but it adds a dependency to javax.script in
camel-core in the OSGi Activator (fine for Java 1.6, new
Hi
On Fri, Jan 14, 2011 at 3:23 AM, Aaron Mulder
ammul...@alumni.princeton.edu wrote:
I would like to get https://issues.apache.org/jira/browse/CAMEL-3481
into the 2.6 release (make camel-script work in OSGi). I have a
solution available, but it adds a dependency to javax.script in
Claus, I will work on friday at CAMEL-3311.
I will also deploy the new camel-aws component into ServiceMix and make some
tests. Maybe I can also add an OSGI integration test.
Christian
Hi
Apache Camel 2.6 starts to look really good. There is only a few tickets left.
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=12311211fixfor=12315690
So if you have any of those tickets assigned, then please
Hi Claus,
I take care of the SMX bundles release today.
I will keep you posted.
Regards
JB
-Original Message-
From: Claus Ibsen claus.ib...@gmail.com
Date: Tue, 11 Jan 2011 09:13:17
To: dev@camel.apache.org
Reply-To: dev@camel.apache.org
Subject: Preparing for Camel 2.6 release
Hi
.
Regards
JB
-Original Message-
From: Claus Ibsen claus.ib...@gmail.com
Date: Tue, 11 Jan 2011 09:13:17
To: dev@camel.apache.org
Reply-To: dev@camel.apache.org
Subject: Preparing for Camel 2.6 release
Hi
Apache Camel 2.6 starts to look really good. There is only a few tickets left
@camel.apache.org
Reply-To: dev@camel.apache.org
Subject: Re: Preparing for Camel 2.6 release
JB,
Last build had 0 failures. I hope it stays like this and I'll start the release
build as soon as the SMX bundles are up.
Thanks,
Hadrian
On Jan 11, 2011, at 3:17 AM, Jean-Baptiste Onofré wrote
37 matches
Mail list logo
