Also looks like this is causing issues with Avatica and bouncycastle on JDK
11:
[ [1;31mERROR [m] error reading
/root/.m2/repository/org/bouncycastle/bcprov-jdk15on/1.55/bcprov-jdk15on-1.55.jar;
invalid manifest format
Kevin Risden
On Thu, Jun 14, 2018 at 9:57 AM, Kevin Risden wrote:
>
I think this might actually be a JDK bug. Let's wait a bit for a new EA
release.
Mit freundlichen Grüßen,
*Christian Beikov*
Am 12.06.2018 um 22:14 schrieb Julian Hyde:
What would be the command-line arguments to achieve
PS Can someone please log a JIRA case for this. At the very least we need to
modify HISTORY.md to say which ES versions are supported with each JDK. If we
can make a code fix, even better.
> On Jun 12, 2018, at 3:14 PM, Julian Hyde wrote:
>
> What would be the command-line arguments to
What would be the command-line arguments to achieve this? I will add them to my
nightly build scripts.
I already skip certain Guava versions based on JDK.
Julian
> On Jun 12, 2018, at 12:42 PM, Kevin Risden wrote:
>
> We might want to skip JDK11 with ES 2.x. 2.x is EOL from Elastic. I can
We might want to skip JDK11 with ES 2.x. 2.x is EOL from Elastic. I can
look into this if it helps.
Kevin Risden
On Tue, Jun 12, 2018, 10:54 Christian Beikov
wrote:
> Seems the latest Java 11 build will be stricter about the manifest
> format when reading. Also see other reports here:
>
> *
Seems the latest Java 11 build will be stricter about the manifest
format when reading. Also see other reports here:
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=535774
*
https://issues.jenkins-ci.org/browse/JENKINS-51871?workflowName=JNJira+%2B+In-Review=1
Not sure if there is anything
Hello everyone
Just I have an issue related to compilation of calcite-elasticsearch2 on
travis
As I see it relates only jdk11 while with others compiles ok
e.g. https://travis-ci.org/apache/calcite/builds/391198921
could anyone please share knowledge how to overcome this?
--
Best regards,
