The Apache Jenkins build system has built Camel.trunk.notest (build #1482)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1482/
to view the results.
+1
On Thu, Dec 29, 2011 at 5:52 AM, Claus Ibsen wrote:
> Hi
>
> Camel 1.x has been EOL for about 1 year now
> http://camel.apache.org/2010/12/17/camel-164-released.html
>
> In our wiki documentation we have sometime parts of the documentation,
> which covers Camel 1.x details only.
>
> I wonder
Thanks Claus.
Probably I missed committing that bit, but cannot test at the moment
though. Sorry for all the noise
Bilgin
On 6 March 2012 10:13, Claus Ibsen wrote:
> Hi
>
> Okay it seems like it was a missing osgi in the pom.xml
> file. I will get this committed when my building completes no
+1
Christian
Sent from a mobile device
Am 06.03.2012 09:07 schrieb "Jean-Baptiste Onofré" :
> +1 it makes sense.
>
> Regards
> JB
>
> On 03/06/2012 08:59 AM, Claus Ibsen wrote:
>
>> On Mon, Mar 5, 2012 at 8:28 PM, Glen Mazza (Talend)
>> wrote:
>>
>>> OK, with Camel 2.0 as the doc base I've been
The Apache Camel project [1] is a powerful open source integration framework
based on known Enterprise Integration Patterns [2].
The Camel PMC made available a new patch release: Apache Camel 2.9.1.
This release includes 109 bug fixes and comes about eight weeks after the
release of camel-2.9.0
Hi
With the latest source from trunk. I get this build error when doing a
full build
mvn clean install -Dtest=false
[ERROR] Failed to execute goal
org.apache.felix:maven-bundle-plugin:2.3.4:bundle (default-bundle) on
project camel-fop: Internal error in maven-bundle-plugin: Illegal
repetition nea
+1 it makes sense.
Regards
JB
On 03/06/2012 08:59 AM, Claus Ibsen wrote:
On Mon, Mar 5, 2012 at 8:28 PM, Glen Mazza (Talend) wrote:
OK, with Camel 2.0 as the doc base I've been removing the Camel 1.x text and
changing text that says "Starting with Camel 2.0, we offer..." to "We
offer..." (sti
On Mon, Mar 5, 2012 at 8:28 PM, Glen Mazza (Talend) wrote:
> OK, with Camel 2.0 as the doc base I've been removing the Camel 1.x text and
> changing text that says "Starting with Camel 2.0, we offer..." to "We
> offer..." (still leaving that terminology for Camel >= 2.1). Next, on our
> component
