Hi Freeman and Cameleers,
we had a brief discussion on this on the dev ML a while back, happy to
discuss it again and see all the pros/cons.
>From my perspective using profiles is not a good idea, it only has an
effect when Camel is built itself, the profiles are not activated when
you bring in a
Hi Zoran,
Just FYI, in CXF we use maven profile which can define JDK9,10,11 specific
dependencies such as jaxb, jaxws, activation and whatnot, probably camel can do
this as well?
Cheers
－
Freeman(Yue) Fang
Red Hat, Inc.
> On Nov 7, 2018, at 5:24 PM, Zoran Regvart wrote:
>
Hi Freeman, Önder and Cameleers,
yeah that's correct, I focused on getting the right dependencies to
build (i.e. compile) on Java 11, we have ~2500 tests failing at the
moment on the CI build[1].
That CI build on the other hand is building on Java 8 and running
tests on Java 11, though I guess at
Hi,
i think all tests are not successful yet.
My first goal was to build with JDK 11 and then i guess we will run the
tests and provide possible fixes for failing ones.
I have got a couple issues while trying to build.
Zoran, did you run local successfull build?
Thanks,
On Wed, Nov 7, 2018 at
Hi Zoran,
I consistently run into error when I use jdk11 to build camel on java-10-test
branch, is it a known issue or I did something wrong?
My java is
java -version
openjdk version "11" 2018-09-25
OpenJDK Runtime Environment 18.9 (build 11+28)
OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed
Hi Cameleers,
So using Groovy 2.5.3 seems to work, I did leave Groovy Eclipse
compiler and the Maven plugin updated to the newer versions.
Also I found that the `maven-shade-plugin` can hang (on Java 11?), so
to work around that I've set `createDependencyReducedPom` to `false`.
Because of this
Hi Pascal & Cameleers,
On Tue, Nov 6, 2018 at 8:23 AM, Pascal Schumacher
wrote:
> No related to camel-core, but this commit
> https://github.com/apache/camel/commit/dda0e4c5890d8e12b5895b8736e3819d0b095d08
> can be reverted/dropped because groovy 2.5.3 should work on Java 11.
Awesome, let me
No related to camel-core, but this commit
https://github.com/apache/camel/commit/dda0e4c5890d8e12b5895b8736e3819d0b095d08
can be reverted/dropped because groovy 2.5.3 should work on Java 11.
Am 06.11.2018 um 03:36 schrieb Onder SEZGIN:
Thanks Zoran. I can see you rebased already i ll try to
Thanks Zoran. I can see you rebased already i ll try to give whole build a
go in a sandbox.
On Fri, Nov 2, 2018 at 4:16 PM Claus Ibsen wrote:
> On Fri, Nov 2, 2018 at 2:04 PM Zoran Regvart wrote:
> >
> > Hi Önder and Cameers,
> > I've just rebased and pushed additional changes on the
On Fri, Nov 2, 2018 at 2:04 PM Zoran Regvart wrote:
>
> Hi Önder and Cameers,
> I've just rebased and pushed additional changes on the `java-10-test`
> branch. With this it should be possible to run:
>
> `./mvnw -Pfastinstall clean install`
>
> on Java 11.
>
> since this is a milestone on getting
Yeah,
not too soon, I just realized that I rebased it wrongly, let me try to
fix that...
zoran
On Fri, Nov 2, 2018 at 2:03 PM, Zoran Regvart wrote:
> Hi Önder and Cameers,
> I've just rebased and pushed additional changes on the `java-10-test`
> branch. With this it should be possible to run:
>
Hi Önder and Cameers,
I've just rebased and pushed additional changes on the `java-10-test`
branch. With this it should be possible to run:
`./mvnw -Pfastinstall clean install`
on Java 11.
since this is a milestone on getting Camel running on Java 11 I guess
I'm going to celebrate this a bit
Hi Önder,
yeah I that would be it; I've not forgotten about this (read: still
rebasing), hopefully will get to the bottom of it today. I hit a snag
with Scala component, and it takes a long time for the build to run...
zoran
On Fri, Nov 2, 2018 at 8:22 AM, Onder SEZGIN wrote:
> Hi Zoran,
> it
Hi Zoran,
it is ok now. apparently as i was not doing full build, i should have
installed parent/pom.xml otherwise camel-parent artifact from snapshot
repository was retrieved where the maven property was missing.
thanks.
On Thu, Nov 1, 2018 at 2:38 PM Onder SEZGIN wrote:
> I think it should
I think it should have been defined. it is in paren/pom.xml.
Not sure why it is not detected.
On Thu, Nov 1, 2018 at 12:08 PM Zoran Regvart wrote:
> Hi Önder,
> looks like the `annotation-api-version` Maven property is not defined.
> Is this on the `java-10-test` branch? I must have missed it
Hi Önder,
looks like the `annotation-api-version` Maven property is not defined.
Is this on the `java-10-test` branch? I must have missed it when
rebasing on `master`, let me rebase and test locally now,
zoran
On Thu, Nov 1, 2018 at 3:19 AM, Onder SEZGIN wrote:
> Hi,
>
> Has anybody tried to
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
17 matches
Mail list logo
