Hi Babak,
I checked the release and it is correct.
My commit was more cleanup than real fix.
So I don't see any release stopper.
Regards
JB
On 12/15/2011 09:17 PM, bvahdat wrote:
Hadrian,
Let me try to explain what the problem I claim to be there:
We assume that the vote will pass and you
+1 (non binding)
Tested in Karaf with a set of example, mostly in blueprint.
I installed all camel features with changes (the ones which use
jetty/war feature in place of the geronimo-servlet, geronimo-jsp,
geronimo-el bundles). Deployment and usage are fine.
Regards
JB
On 12/15/2011 03:20 P
I just ran the tests with Camel in Action code, they are looking good.
Here is my +1.
Willem
On 12/15/11 10:20 PM, Hadrian Zbarcea wrote:
A new release candidate apache-camel-2.9.0 final is out with
approximately 464 issues resolved so far: improvements and bug fixes [1].
Please find the stagi
Hi Babak
Before hadrian did the Camel 2.9.0 release, I ran the mvn clean install
-Pvalidate to check the feature file and I also enabled the -Pvalidate
profile when running the release:prepare few weeks ago.
They are helping us to find out any issue of apache-camel feature.
I just checked th
Hi Babak,
For the commit of CAMEL-4768 and CAMEL-4675 were not suppose to be
committed. Here must be something wrong with my git repo when I run the
git svn dcommit.
And these commits are harmless for the release as we already committed
the whole patches.
On 12/15/11 10:51 PM, bvahdat wrot
Hadrian,
Let me try to explain what the problem I claim to be there:
We assume that the vote will pass and you will promote/copy the staging repo
content to the central repo and announce the release officially on the Wiki
& maybe even on the User-Forum, right?
Now as an example through the revis
Babak, the jira release is actually not today, it's when the vote closes
successfully (Monday if no -1s). Also some jiras have multiple fix
versions (like the not yet released 2.8.4) and some commits target such
release.
I hope I didn't misunderstand your point,
Hadrian
On 12/15/2011 09:51 A
Hi,
In the context of the tickets below (Fix Version 2.9.0 in JIRA), I see
changes made on the trunk which are to be already included by the 2.9.0
final release (but all are *after* the release today @ 15.12.11 05:12 by
Hadrian, see [1]).
https://issues.apache.org/jira/browse/CAMEL-4777
https://
A new release candidate apache-camel-2.9.0 final is out with
approximately 464 issues resolved so far: improvements and bug fixes [1].
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapachecamel-343/
The tarballs are here
https://repository.apache.org/co
Hi Hadrian,
could you provide the URL of the staging repo ?
I'm afraid that I found an issue in the features.xml (also present in
Camel 2.8.x): the commons-codec property wasn't correct (${commons-code}
in place of ${commons-codec}).
I fixed it in both trunk and camel-2.8.x branch.
I would
10 matches
Mail list logo
