The Apache Jenkins build system has built Camel.trunk.notest (build #2329)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2329/
to view the results.
There are already some discussions on board@ and a couple other places about
what to do with the various apache-extras things. I’d wait until they decide
on those issues.
Dan
> On Mar 12, 2015, at 10:11 PM, Willem Jiang wrote:
>
> Hi,
>
> I got a mail from google said the Google code wi
Is it not possible to put this under camel repo as extra's in a separate folder
like components?
> Date: Fri, 13 Mar 2015 10:11:49 +0800
> From: willem.ji...@gmail.com
> To: dev@camel.apache.org
> Subject: Moving camel-extra to github
>
> Hi,
>
> I got a
Hi,
I got a mail from google said the Google code will be shutdown shortly. As we
host the camel-extra in Google Code, it’s the time to think about moving the
repository into Github?
Google code already provides a tool to export the project into Github, the
question is do we need to great a ne
Hi Willem,
Is it possible to change the link path itself?
I think changing it from* href="faq.html" *to* href="/faq.html" *should fix
this issues and links will be working from both camel home page and blog
page. (Same should be done for all other links)
On Thu, Mar 12, 2015 at 5:39 AM, Willem
Hi,
The side bar links are relative links, they are not work in the blog page.
If you want to access the FAQ, you can access it from the home page. I tried to
remove the side bar from the blog page, but I didn’t find a way to do it.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blo
