Agree about this might be a JDK bug.

https://bugs.openjdk.java.net/browse/JDK-8200530

and followed up by

https://bugs.openjdk.java.net/browse/JDK-8204494

I checked the Netty Manifest file and it uses /r/n.

This should be fixed in build 18 and was broken in build 17.

Kevin Risden

On Tue, Jun 12, 2018 at 11:33 PM, Christian Beikov <
[email protected]> 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 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 <[email protected]> wrote:
>>>
>>> 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 <[email protected]
>>> >
>>> wrote:
>>>
>>> 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?workflowN
>>>> ame=JNJira+%2B+In-Review&stepId=1
>>>>
>>>> Not sure if there is anything you can do. I'd assume other tests that
>>>> use e.g. Netty would fail compilation as well.
>>>>
>>>> Mit freundlichen Grüßen,
>>>> ------------------------------------------------------------
>>>> ------------
>>>> *Christian Beikov*
>>>> Am 12.06.2018 um 14:11 schrieb Sergey Nuyanzin:
>>>>
>>>>> 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?
>>>>>
>>>>>
>>>>
>

Reply via email to