For those who are interested:
There was indeed a difference in the JDK version per OS: On Windows it was
JDK-16+24, while Ubuntu was already on JDK-16+30.
In JDK-16+28 the changes for JEP 396[1] were added, meaning "Strongly
Encapsulate JDK Internals by Default"
This has been a known issue for Gr
Thanks for the update Sylwester
Rgds,Rory
On 10/02/2021 14:12, Sylwester Lachiewicz wrote:
Hi,
we fixed our integration tests for Maven components with Groovy and
few old plugin updates.
Other than that we have only known failures - not related to JDK 16.
Best regards,
Sylwester
pon., 8 l
Hi,
we fixed our integration tests for Maven components with Groovy and
few old plugin updates.
Other than that we have only known failures - not related to JDK 16.
Best regards,
Sylwester
pon., 8 lut 2021 o 11:50 Rory O'Donnell napisał(a):
>
> Hi Robert,
>
> Looks like logging a Groovy bug mak
Hi Robert,
Looks like logging a Groovy bug makes the most sense ?
Do keep us updated.
Rgds,Rory
On 07/02/2021 13:13, Robert Scholte wrote:
I've asked ASF Infra so install the latest JDK 16-ea.
They confirmed there was a difference between Windows and Ubuntu:
"Right, we have ea30 on Ubuntu and
I've asked ASF Infra so install the latest JDK 16-ea.
They confirmed there was a difference between Windows and Ubuntu:
"Right, we have ea30 on Ubuntu and ea24 on Windows currently, will update."
In the meantime I've rerun the build including the stacktrace:
Caused by: java.lang.ExceptionInInitial
Hi Robert,
There's no stack trace so can't see if it's Groovy or something else
hacking the JDK ?
Probably best to log a bug with as much info as possible, version of
Groovy etc.
Thanks,Rory
On 05/02/2021 19:15, Robert Scholte wrote:
I've been to reproduce it again:
Jenkins: https://ci-b
I've been to reproduce it again:
Jenkins: https://ci-builds.apache.org/job/Maven/job/jdk16-ea/2/console
Sources: https://github.com/rfscholte/jdk16-ea
Most important lines:
Failed to execute goal org.codehaus.gmaven:gmaven-plugin:1.4:execute (default)
on project mcompiler-182: Execution default
Hi Rory,
I hope I can isolate the issue and come with a clear description.
thanks,
Robert
On 5-2-2021 17:18:11, Rory O'Donnell wrote:
Hi Robert,
Could you log a bug and send the JI number ?
Thanks, Rory
On 05/02/2021 11:45, Rory O'Donnell wrote:
> Hi Robert,
>
> I've been asked if you can pro
Hi Robert,
Could you log a bug and send the JI number ?
Thanks, Rory
On 05/02/2021 11:45, Rory O'Donnell wrote:
Hi Robert,
I've been asked if you can provide a link to the exception, we can't
immediately find it on your Jenkins.
If we can get to the stack trace then it might reveal a bit mor
Hi Robert,
I've been asked if you can provide a link to the exception, we can't
immediately find it on your Jenkins.
If we can get to the stack trace then it might reveal a bit more. The
temporary workaround is to open java.lang of course.
Rgds,Rory
On 05/02/2021 11:18, Robert Scholte wrote:
Hi Rory,
we're seeing some projects failing due to JDK16 + Linux[1], and I think they
all have a similar issue.
The error looks like this:
Unable to make public java.lang.AbstractStringBuilder
java.lang.AbstractStringBuilder.append(char[],int,int) accessible: module
java.base does not "opens ja
*Hi Robert , *
*Per the JDK 16 schedule , we are in the Release Candidate Phase**[1] .*
*Please advise if you find any issues while testing the latest Early
Access builds.*
* Schedule for JDK 16
o *2021/02/04 Initial Release Candidate*
o 2021/02/18 Final Release Candidate
o 2
12 matches
Mail list logo
