The Apache Jenkins build system has built Camel.2.12.x.notest (build #103)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.2.12.x.notest/103/
to view the results.
The Apache Jenkins build system has built Camel.2.13.x.notest (build #13)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.2.13.x.notest/13/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest (build #2083)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2083/
to view the results.
Hi
Yeah that’s normal, only the major/minor releases are published but not the
patch releases where “current” is a symbolic link to the latest/newest one.
http://camel.apache.org/maven/
Babak
Antoine DESSAIGNE wrote
> Hi everyone,
>
> I've just noticed that the official javadoc [1] is referen
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/185
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/184
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Just a heads up that we got a bunch of CS issues on master. It seems
related to the new camel-component-api
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://
Great, thanks!
Actually I was not aware of all these CXF goodies being embedded into the
Camel website, so next time I will for sure ask for your help if I don’t
know any further.
BTW wiping out the cache doesn't seem to be that wrong as I thought
http://camel.465427.n5.nabble.com/svn-commit-r8305
GitHub user kevinearls opened a pull request:
https://github.com/apache/camel/pull/185
Fix for CAMEL-7512 Expose the component options for Camel Netty
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kevinearls/camel CAMEL-7512
A
On Jun 16, 2014, at 11:12 AM, Babak Vahdat wrote:
> This's the way we've been told to force a sync:
>
> http://camel.465427.n5.nabble.com/The-sync-between-our-wiki-and-the-site-td5742046.html
>
> And I guess the best we could do next time is to raise a ticket @ INFRA for
> them to debug/look i
Hi everyone,
I've just noticed that the official javadoc [1] is referencing camel 2.13.0
instead of the latest one. Is it normal ?
Thanks,
Antoine.
[1] http://camel.apache.org/maven/current/camel-core/apidocs/index.html
This's the way we've been told to force a sync:
http://camel.465427.n5.nabble.com/The-sync-between-our-wiki-and-the-site-td5742046.html
And I guess the best we could do next time is to raise a ticket @ INFRA for
them to debug/look into such things.
Babak
dk...@apache.org wrote
> On Jun 16, 201
GitHub user kevinearls opened a pull request:
https://github.com/apache/camel/pull/184
Fix for CAMEL-7511 Expose the component options for Camel Quartz2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kevinearls/camel CAMEL-7511
On Jun 16, 2014, at 1:07 AM, Jan Matèrne (jhm) wrote:
> Ok, so after a change: wait a day and then post a note if the sync has not
> happened.
And preferrably, instead of wiping out the cache to regenerate, help debug the
process that is supposed to detect changes to figure out why it didn’t…
GitHub user kevinearls opened a pull request:
https://github.com/apache/camel/pull/183
Fix for CAMEL-7510 Expose the component options for Camel Quartz
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kevinearls/camel CAMEL-7510
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/182
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Yeah, why not. It could be interesting to know who will join us in
Budapest. Please go ahead...
Best,
Christian
On Fri, Jun 13, 2014 at 8:45 AM, Jan Matèrne (jhm)
wrote:
> Just an idea: a wiki page where camel-guides could add their name if
> they'll attend.
> Maybe with some proposals for me
GitHub user kevinearls opened a pull request:
https://github.com/apache/camel/pull/182
Fix for CAMEL-7509 Expose the component options for Camel JGroups
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kevinearls/camel CAMEL-7509
Works for me (tried updating browser cache - success).
Jan
> -Ursprüngliche Nachricht-
> Von: Antoine DESSAIGNE [mailto:antoine.dessai...@gmail.com]
> Gesendet: Montag, 16. Juni 2014 08:42
> An: Camel Development
> Betreff: Re: AW: Confluence -> Manual
>
> Hi,
>
> The http://camel.apach
19 matches
Mail list logo
