[ 
https://issues.apache.org/jira/browse/PIVOT-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062797#comment-17062797
 ] 

Roger Lee Whitcomb commented on PIVOT-1043:
-------------------------------------------

I'm trying to build latest "trunk" using AdoptOpenJDK 11.0.6 on Windows, 
targeted for "release 8" (not sure if this makes a difference or not):
{code:java}
openjdk version "11.0.6" 2020-01-14 OpenJDK Runtime Environment AdoptOpenJDK 
(build 11.0.6+10) OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.6+10, mixed 
mode){code}
And getting this error:
{code:java}
    [javac] 
C:\Projects\pivot\trunk\wtk\src\org\apache\pivot\wtk\BrowserApplicationContext.java:28:
 error: package netscape.javascript does not exist
    [javac] import netscape.javascript.JSObject;
    [javac]                           ^{code}
I am NOT, however, getting any errors building on OSX with the straight OpenJDK 
11:
{code:java}
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 mode){code}
This concerns me, because the OpenJDK is *supposed* to be a lot more compatible 
with the paid Oracle versions now, but there is this huge blocker issue 
(difference) now, plus the newer version is "broken", while the earlier one (or 
Mac version, not sure what the difference might be) is okay.

> Investigate Java 11 compatibility
> ---------------------------------
>
>                 Key: PIVOT-1043
>                 URL: https://issues.apache.org/jira/browse/PIVOT-1043
>             Project: Pivot
>          Issue Type: Bug
>            Reporter: Roger Lee Whitcomb
>            Assignee: Roger Lee Whitcomb
>            Priority: Major
>             Fix For: 2.1.0
>
>
> Trying to run a Pivot application under OSX using OpenJDK Java 11 version 
> gives this error on the console:
> Unable to attach EAWT hooks: java.lang.ClassNotFoundException: 
> com.apple.eawt.ApplicationListener
> Everything appeared to work correctly, so I'm thinking this API call can just 
> go away for Java 11.  But it should be investigated.
> Other things with Java 11 might come up too, so this is a placeholder for 
> them too.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to