+1
On Thu, Jul 5, 2012 at 11:55 PM, Christian Müller
wrote:
> I would like to change the license headers in camel-extra to something like
> the following (I took the original GNU GPL v2 license header and added the
> camel specific parts):
>
> /
On Sun, Jul 8, 2012 at 12:15 PM, 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 that the svn merge
> tool works? It would be nice if this step is documented in the WIKI so that
> every comm
+1
Christian
Am 05.07.2012 22:07, schrieb Christian Müller:
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.org/content/repositories/orgapachecamel
+1.
Willem
On 7/6/12 4:07 AM, Christian Müller 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.org/content/repositories/orgapachecamel-031/
I know I'm late to this discussion, but I wanted to throw my 2 cents
in. I do not see the value in enforcing valid URIs within Camel. I
fully agree that, in this case, ease of use trumps strictly adhering to
a standard.
At Raytheon, we're using Camel as mediation between UIs, power
electron
> The last thing I want to check before we release camel-extra 2.10.0 is
> generating the asc files as we do it for our regular Apache Camel releases.
I can handle this too. I hope I can do it this week (before my holidays).
--
Henryk Konsek
http://henryk-konsek.blogspot.com
+1
Babak
Christian Mueller 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.org/content/repositories/orgapachecamel-031/
>
> The
Could somebody of the core committers create a new camel-2.10.x release
branch and set/adjust the svn properties accordingly so that the svn merge
tool works? It would be nice if this step is documented in the WIKI so that
every committer could do this (creating the branch is not a big deal but
set
Here is my +1
I updated the Camel in Action source (rev 334 - the last one before it was
upgraded to 2.9.0) to work with Camel 2.8.6 and all test except the TX
tests passed (they failed on my machine also for previous Camel 2.8.x
releases). No problem with this.
I could successfully install all Ca
+1
On Thu, Jul 5, 2012 at 10:07 PM, Christian Müller
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.org/content/repositories/orgapac
10 matches
Mail list logo
