Re: [Netrexx-develop] Beta of NetRexx 4.02 and modern JDK woes

[René J. <rvj...@xs...>]

Ok, I will proceed with preparing 4.02 BETA. But nothing is closed yet, so if you feel inspired, just commit to the repo.

For all who build NetRexx themselves:

Last night I checked in a change that enables an ANT build of NetRexx under Java 18 or 19. I seems that the Java SecurityManager, which was deprecated for a number of release, has been taken out and the warning that it should not be used has become an exception.
The task impacted is the <java> task that is used to start the DiagAll class for testing after building. If this is done without forking a new VM, ANT decides to put a SecurityManager on the process, which it will remove after the task. Although this was known for more than 6 months, it was not fixed by the ANT team yet - the current patch in the NetRexx build.xml file is just a workaround gleaned from the Apache ANT bug database, and specifies fork=yes - that *is* a narrow escape.

Also be aware that Java has become a moving target in Oracle’s hands and - maybe with the best of intentions - a lot of breakage occurs. So we need to get our testing more structured than it was. As jUnit also turned out to be something that is eager to introduce all kinds of new and shaky Java tech (annotations for no good reasons etc) I am planning to move the newer tests back into the tried & true Diag package. If you work on new stuff, just add the tests to Diag - as Marc already very sensibly did.

At the moment I am trying to fix the parts of the documentation that use the JSR223 component, as that still needs Java8 to build it (the output from the examples is built ‘live’ by TeX so it is always up to date - but up to date means broken for the newer JDK’s.

Best regards,

René.

> On 6 Jan 2022, at 10:10, Marc Remes <re...@gm...> wrote:
> 
> Hi René,
> 
> nothing to add from my side.
> ADDRESS with stem seems a good idea, I could take a look at that, but that would be for a next release.
> And maybe I can take a look at Docker, but also not now;
> 
> All the best for 2022 !
> 
> Marc
> 
> 
> On 1/5/22 21:17, René Jansen wrote:
>> For the developers: is there something that needs including in the BETA for 4.02?
>> I was aiming for December 31 but obviously I did not make that; with some doc changes I will be doing today the beta is nearly ready.
>> I was thinking about:
>> Address with stem/arraylist/indexed string
>> SPECS change to replicate CMS bugs
>> More RxModel implementations?
>> ?
>> Let me know!
>> I was planning to build Docker images again for 4.02, but I am vexed with Pipelines not working within a container. Anybody any thoughts, or time to look into that?
>> Best regards,
>> René.
>> _______________________________________________
>> Netrexx-develop mailing list
>> Net...@li...
>> https://lists.sourceforge.net/lists/listinfo/netrexx-develop