> From: Mark Thomas [mailto:ma...@apache.org]
> Subject: Re: JDK 12 , JDK 8u202 & Project Panama Early-Access builds
available
> I tried using a different header file with (hopefully) more functionality:
> /opt/java/openjdk-12-panama-b0/bin/jextract \
> -I include \
&g
On 10/11/2018 11:00, Mark Thomas wrote:
> Thanks to some off-list help from Chuck, I have been able to make some
> progress on this. The following:
>
> /opt/java/openjdk-12-panama-b0/bin/jextract \
> -I include \
> -I /usr/lib/gcc/x86_64-linux-gnu/7.3.0/include \
> -I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
On 11/9/18 07:38, Mark Thomas wrote:
> On 09/11/2018 10:57, Rory O'Donnell wrote:
>
>
>
>> *Project Panama Early-Access build 0 ***is available at : -
>> http://jdk.java.net/panama/
>
> This looks interesting. If I am reading the
On 09/11/2018 18:54, Mark Thomas wrote:
> On 09/11/2018 12:38, Mark Thomas wrote:
>> On 09/11/2018 10:57, Rory O'Donnell wrote:
>>
>>
>>
>>> *Project Panama Early-Access build 0 ***is available at : -
>>> http://jdk.java.net/panama/
>>
>> This looks interesting. If I am reading the information
On 09/11/2018 12:38, Mark Thomas wrote:
> On 09/11/2018 10:57, Rory O'Donnell wrote:
>
>
>
>> *Project Panama Early-Access build 0 ***is available at : -
>> http://jdk.java.net/panama/
>
> This looks interesting. If I am reading the information correctly, it
> could reduce the scope of Tomcat
Thanks for the update Mark!
On 09/11/2018 14:05, Mark Thomas wrote:
On 09/11/2018 10:57, Rory O'Donnell wrote:
Hi Mark,
*JDK 12 Early Access build 19 is available at : - jdk.java.net/12/*
Built Tomcat 9.0.x and an all the unit tests. All passed.
Mark
On 09/11/2018 10:57, Rory O'Donnell wrote:
> Hi Mark,
>
> *JDK 12 Early Access build 19 is available at : - jdk.java.net/12/*
Built Tomcat 9.0.x and an all the unit tests. All passed.
Mark
-
To unsubscribe, e-mail:
On 09/11/2018 10:57, Rory O'Donnell wrote:
> *Project Panama Early-Access build 0 ***is available at : -
> http://jdk.java.net/panama/
This looks interesting. If I am reading the information correctly, it
could reduce the scope of Tomcat Native or even remove it completely
(assuming we dropped
