+1.
Willem
On Tuesday, October 30, 2012 at 7:41 PM, Claus Ibsen wrote:
> See ticket: https://issues.apache.org/jira/browse/CAMEL-5534
>
> In camel-spring we have a single @deprecated class that was part of
> the earlier days (Camel 2.8 and older) where some Camel components was
> dependent o
+1 for removing the @deprecated classes.
Best,
Christian
On Tue, Oct 30, 2012 at 12:41 PM, Claus Ibsen wrote:
> See ticket: https://issues.apache.org/jira/browse/CAMEL-5534
>
> In camel-spring we have a single @deprecated class that was part of
> the earlier days (Camel 2.8 and older) where som
Yeah, that's what I was looking for.
But the other option is good for the builds which failed in the past...
Christian
On Tue, Oct 30, 2012 at 11:29 PM, David Karlsen wrote:
> Another [maybe more obvious] option (for more ad-hoc stuff) is to
> browse the workspace - but that will only contain th
Another [maybe more obvious] option (for more ad-hoc stuff) is to
browse the workspace - but that will only contain the current
situation and not the history.
2012/10/30 Christian Müller :
> Thanks for the hint David!
> I configured the Camel.2.10.x.fulltest to archive the log files too.
>
> Thank
Thanks for the hint David!
I configured the Camel.2.10.x.fulltest to archive the log files too.
Thanks again,
Christian
On Tue, Oct 30, 2012 at 10:09 AM, David Karlsen wrote:
> You could configure the job to archive the log-files - then they
> should appear under archived artifacts.
>
> 2012/10/
Am 30.10.12 12:41 schrieb "Claus Ibsen" unter :
>See ticket: https://issues.apache.org/jira/browse/CAMEL-5534
>
>In camel-spring we have a single @deprecated class that was part of
>the earlier days (Camel 2.8 and older) where some Camel components was
>dependent on Spring.
>
>We have these clas
+1 on removing the deprecated classes.
Hadrian
On 10/30/2012 07:41 AM, Claus Ibsen wrote:
See ticket: https://issues.apache.org/jira/browse/CAMEL-5534
In camel-spring we have a single @deprecated class that was part of
the earlier days (Camel 2.8 and older) where some Camel components was
depe
Hi,
In revisions 949, 950 and 951 I rollbacked the 2.10.0 release and
refactored package 'org.apachextras' to 'org.apacheextras'.
Tomorrow I'll stage another 2.10.0 release candidate.
Best regards.
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Thanks, Willem!
-Original Message-
From: Willem jiang [mailto:willem.ji...@gmail.com]
Sent: Friday, October 26, 2012 10:18 PM
To: dev@camel.apache.org
Subject: Re: Camel cold restart via JMX
Hi Daniel,
I will take care of the patch today.
--
Willem Jiang
Red Hat, Inc.
FuseSource i
Hi Willem (or anybody else), could we have more detail added concerning
the new SMPP addressRange option, here is what we have:
https://cwiki.apache.org/confluence/pages/diffpages.action?pageId=9012014&originalId=30739775
A few questions:
1.) What does the default value of "" indicate?
2.) Can/s
See ticket: https://issues.apache.org/jira/browse/CAMEL-5534
In camel-spring we have a single @deprecated class that was part of
the earlier days (Camel 2.8 and older) where some Camel components was
dependent on Spring.
We have these classes in org.apache.camel.component from Spring. They
are al
Thanks for fixing it!
Best,
Christian
Sent from a mobile device
Am 30.10.2012 08:18 schrieb "Claus Ibsen" :
> Hi
>
> I think this is fixed now, the import range is now 1.6 onwards. It
> seems there was a problem if you have the
> ${camel.osgi.import.defaults}, to early in the osgi imports in the
You could configure the job to archive the log-files - then they
should appear under archived artifacts.
2012/10/30 Christian Müller :
> Hello Dan, hello list,
>
> do you know whether there is a way to access the Camel log files on
> build.apache.org even I'm not a Jenkins admin? I'm asking becaus
Hi
I think this is fixed now, the import range is now 1.6 onwards. It
seems there was a problem if you have the
${camel.osgi.import.defaults}, to early in the osgi imports in the
pom.xml. Having ${camel.osgi.import.defaults}, at the end resolves
many of the issues.
On Mon, Oct 29, 2012 at 3:36 P
Hello Dan, hello list,
do you know whether there is a way to access the Camel log files on
build.apache.org even I'm not a Jenkins admin? I'm asking because some of
the unit tests are brittle and are failing from time to time on our CI
server. Because we turned off the console logging by default,
15 matches
Mail list logo
