I've experimented a bit with jitpack.io to get the Java 10 build running.
I've created a branch/build to test this using the daily build, the
build failed but I think it's because the node was disconnected from
Jenkins -- but the Java 10 stage of the build was successfully built
according to the logs.
I can merge this to master, but it will tie us to jitpack.io until
there is a new MVEL release with the fix we need.
a little update on this effort. Over the past few days I've been
adding dependencies and fixing issues in tooling that I've found while
running the build on early access Java 11 builds.
You can follow/contribute to this effort on the, not very cleverly
named, `java-10-test` branch. I think, working incrementally so some
failures might occur on modules whose dependencies changed after I've
gone through them, that Camel can now build on Java 11.
Next effort is on adding dependencies needed for test and running the
tests in the daily build.
Right now I've disabled Java 9 build and I'm just looking into Java 10
& 11 in a, not very cleverly named, Camel.daily-zregvart Jenkins
There are two commits that I'm not sure if we would like to merge into
master once this is done, both are using patched versions of MVEL
I think that APT tooling commit can be merged into master. And that
once I add the required test dependencies the dependency modification
commit can be merged after that.
I would appreciate any input on the method I'm doing this (adding
dependencies via Maven profile), the dependencies them selves as there
are plenty of options to choose on Maven central.
I'll start another thread on what Java versions we wish to support.