+1 to do it with a shell script.
On Fri Dec 30 15:31:58 2011, Jean-Baptiste Onofré wrote:
Hi Christian,
I'm not sure it's a good idea (lot of work, sync, etc). I would prefer
documenting how to do that directly in Karaf directly using a shell
script (with features:list |grep -i camel && featu
Hi Christian,
I'm not sure it's a good idea (lot of work, sync, etc). I would prefer
documenting how to do that directly in Karaf directly using a shell
script (with features:list |grep -i camel && features:install {} or so).
Regards
JB
On 12/29/2011 11:25 PM, Christian Müller wrote:
What d
Hi Christian,
I don´t think that would help much. Our recent problem where some
dependencies where missing would
not have shown in a camel-all feature as in sum they were there. For
users it is also not practical as installing
all camel-modules takes long and consumes a lot of memory.
So I ra
I think that'll be a whole lotta work for something you can do in awk or perl
in about 2 seconds….
Just my .2
On Dec 29, 2011, at 3:25 PM, Christian Müller wrote:
> What do you think about a "camel-all" features which installs all available
> Camel features with one command? This make it more e
The Apache Jenkins build system has built Camel.trunk.notest (build #1423)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1423/
to view the results.
What do you think about a "camel-all" features which installs all available
Camel features with one command? This make it more easy to install all
Camel features in Karaf/SMX and see if it works.
Best,
Christian
+1
Installed successfully the features in Karaf 2.2.5 (with the
jre.properties.cxf)
Best,
Christian
On Wed, Dec 28, 2011 at 4:36 AM, Hadrian Zbarcea wrote:
> A new release candidate apache-camel-2.9.0 final is out with approximately
> 497 issues resolved so far: improvements and bug fixes [1].
+1
On Thu, Dec 29, 2011 at 10:22 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
+1
Em 29/12/2011 13:26, "Johan Edstrom" escreveu:
> +1
>
> On Dec 29, 2011, at 3:54 AM, Jean-Baptiste Onofré wrote:
>
> > +1
> >
> > Fully agree,
> >
> > Regards
> > JB
> >
> > On 12/29/2011 10:22 AM, Claus Ibsen wrote:
> >> Hi
> >>
> >> Camel 1.x has been EOL for about 1 year now
> >> http://cam
Hi,
IMHO much worse than the grammer errors are the semantic errors all over the
places where the classes have been refactored from package X to Y without
adjustment of their description. If these corrections are not done at the right
time, namley when committing, then it becomes just a matter
+1
Regards
JB
On 12/28/2011 04:08 PM, Claus Ibsen wrote:
Hi
The camel-test component supports currently both JUnit 3.x and 4.x,
each in separate package.
Supporting both requires us to have a fair amount of duplicated code,
one for 3.x and another for 4.x.
I suggest to @deprecated the JUnit 3
+1 (non binding)
Tested with a blueprint routes in Karaf without problem.
Regards
JB
On 12/28/2011 04:36 AM, Hadrian Zbarcea wrote:
A new release candidate apache-camel-2.9.0 final is out with
approximately 497 issues resolved so far: improvements and bug fixes [1].
Please find the staging re
+1
On Dec 29, 2011, at 3:54 AM, Jean-Baptiste Onofré wrote:
> +1
>
> Fully agree,
>
> Regards
> JB
>
> On 12/29/2011 10:22 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 documentat
Built and deployed with karaf and some custom tests
+1
On Dec 29, 2011, at 7:18 AM, Claus Ibsen wrote:
> Gave it a test run with the Camel in Action source code.
>
> +1
>
> On Wed, Dec 28, 2011 at 4:36 AM, Hadrian Zbarcea wrote:
>> A new release candidate apache-camel-2.9.0 final is out wit
+1 on both counts.
Hadrian
On 12/29/2011 12:54 AM, Willem Jiang wrote:
Here is my +1.
BTW, camel-core unit tests are using the JUnit3 classes because we don't
have the API module to let the camel-test depends on.
I think we can address it in Camel 3.0.
On Thu Dec 29 10:09:29 2011, Daniel Kulp
Gave it a test run with the Camel in Action source code.
+1
On Wed, Dec 28, 2011 at 4:36 AM, Hadrian Zbarcea wrote:
> A new release candidate apache-camel-2.9.0 final is out with approximately
> 497 issues resolved so far: improvements and bug fixes [1].
>
> Please find the staging repo here:
>
Ran some tests with the kit today, they are looking good.
Here is my +1.
Willem
On Wed Dec 28 11:36:30 2011, Hadrian Zbarcea wrote:
A new release candidate apache-camel-2.9.0 final is out with
approximately 497 issues resolved so far: improvements and bug fixes [1].
Please find the staging re
+1
Fully agree,
Regards
JB
On 12/29/2011 10:22 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 wonde
+1
I also have started removing references to 1.x stuff.
Christian
Am 29.12.2011 10:22, schrieb Claus Ibsen:
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
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 if we should start removing those pieces?
For example when I from time to
Hi
Ticket created
https://issues.apache.org/jira/browse/CAMEL-4840
On Wed, Dec 28, 2011 at 4:08 PM, Claus Ibsen wrote:
> Hi
>
> The camel-test component supports currently both JUnit 3.x and 4.x,
> each in separate package.
> Supporting both requires us to have a fair amount of duplicated code,
21 matches
Mail list logo
