Hi,
Has anybody tried to build camel-core locally with JDK-11?
First i got this error;
[ERROR] Failed to execute goal
org.apache.camel:camel-package-maven-plugin:2.23.0-SNAPSHOT:prepare-spring-boot-auto-configuration
(validate) on project camel-core: Execution validate of goal
org.apache.camel:c
Hi Cameleers,
there are test failures in the `camel-spring-cloud-consul`[1], to me
it seems like an issue with Spring Boot auto-configuration:
`ConsulDiscoveryClientConfiguration::heartbeatProperties` and
`ConsulServiceRegistryAutoConfiguration::heartbeatProperties` try to
define the same bean, whe
Hi Tadayoshi & Cameleers,
any changes you make on the `camel-website` on the `asf-site` branch
will get overwritten by the build job[1] for the `website` branch in
the `camel` repository. So you need to do all the work on the
`website` branch in the `camel` git repository.
I'm still trying to find
Hi Francois & Cameleers,
don't be sorry, we appreciate all the help, the website is long
overdue mostly because we all can't find the time to work on it...
zoran
On Wed, Oct 31, 2018 at 7:14 AM, Francois Papon
wrote:
> Hi,
>
> It's great, thanks Zoran!
>
> I can take a look about the breaking C
Hi Nicola & Cameleers,
On Wed, Oct 31, 2018 at 8:49 AM, Nicola Ferraro wrote:
> It would be technically possible to have both websites persisted on master,
> so that we just swap them when the new one is ready?
Yes, they are independent.
The current website at camel.apache.org published via bui
It sounds good to me: having several hands and help.
I'm working on new stuff around OSGi/Karaf for Camel.
Regards
JB
On 31/10/2018 07:14, Francois Papon wrote:
> Hi,
>
> It's great, thanks Zoran!
>
> I can take a look about the breaking CSS and links.
>
> I'm sorry, I was very busy this mont
Great work. Thanks Zoran.
On Wed, Oct 31, 2018 at 10:49 AM Nicola Ferraro
wrote:
> That's nice Zoran. I think it's a good first step is to have something that
> is displayed on the web, so that we can iterate.
>
> It would be technically possible to have both websites persisted on master,
> so t
nicolaferraro closed pull request #200: Cannot configure traits
URL: https://github.com/apache/camel-k/pull/200
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (fr
nicolaferraro closed issue #199: Cannot configure traits
URL: https://github.com/apache/camel-k/issues/199
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
That's nice Zoran. I think it's a good first step is to have something that
is displayed on the web, so that we can iterate.
It would be technically possible to have both websites persisted on master,
so that we just swap them when the new one is ready?
Nicola
On Wed, Oct 31, 2018 at 7:15 AM Fra
10 matches
Mail list logo
