You can subscribe to this list here.
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(11) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2020 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
(2) |
2022 |
Jan
(28) |
Feb
(6) |
Mar
(14) |
Apr
(4) |
May
|
Jun
(6) |
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
(4) |
2023 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
From: Rony G. F. <Ron...@wu...> - 2022-01-27 14:10:46
|
It will be the case that over time more and more Java class libraries will not function anymore because of the removal of APIs, components and increase of security measurements. One interesting Java class library that cannot be used starting with Java 11 is "jni4net" which is the bridge between Java and .Net/CLR as it utilizes "runFinalizersOnExit" which got removed in OpenJDK/Java 11. The latest version of the jni4net library is at 0.8.8, cf. <https://github.com/jni4net/jni4net/releases>, released on 2014-09-23. So indeed supporting Java 8 will allow NetRexx to be viable for that platform in the years to come. ---rony On 27.01.2022 15:04, Rony G. Flatscher wrote: > > It may be interesting/helpful sometimes to get to see which Java APIs and which Java tools and > components get removed in which version of Java, which Oracle briefly describes as per OpenJDK 17 > LTS: > > * APIs > <https://docs.oracle.com/en/java/javase/17/migrate/removed-apis.html#GUID-A7ABC76A-5037-4052-8718-562923FC7028> > * tools and components > <https://docs.oracle.com/en/java/javase/17/migrate/removed-tools-and-components.html#GUID-F182E075-858A-4468-9434-8FC1704E7BB7> > > ---rony > > > On 27.01.2022 14:53, Rony G. Flatscher wrote: >> On 27.01.2022 13:53, Marc Remes wrote: >>> And a side note.. >>> You need java 9 or above to compile and run this. >>> >>> Which brings up another topic : are we ready to stop supporting java 8? >> Please no, unless you want to remove most of the Java installed base for NetRexx. >> :) >> >> Seriously, NetRexx should support Java 8 as long as Java 8 gets supported by OpenJDK distributors. >> E.g. Oracle and Azul support Java 8 until December 2030, for very good reasons! Actually Java 8 gets >> currently a longer support than Java 11 LTS and Java 17 LTS, believe it or not. >> >> [BSF4ooRexx still supports Java 6 as its baseline (that is the reason for "6" in "641", "41" means >> ooRexx baseline is version 4.1) as there are companies/organizations that have still Java 6 >> deployed. This incurs quite some overhead and support efforts as in Java 6 one needs to use >> java.lang.reflect whereas starting with Java 9 one must use java.lang.invoke instead (actually >> BSF4ooRexx uses by default java.lang.invoke starting with Java 8 as Java 7, where this package got >> introduced, has some missing support in that area).] >> >> In general a good overview of the support dates for different versions of Java by different >> distributors can be found here: <https://en.wikipedia.org/wiki/Java_version_history>. >> >> ---rony >> |
From: Rony G. F. <Ron...@wu...> - 2022-01-27 14:04:16
|
It may be interesting/helpful sometimes to get to see which Java APIs and which Java tools and components get removed in which version of Java, which Oracle briefly describes as per OpenJDK 17 LTS: * APIs <https://docs.oracle.com/en/java/javase/17/migrate/removed-apis.html#GUID-A7ABC76A-5037-4052-8718-562923FC7028> * tools and components <https://docs.oracle.com/en/java/javase/17/migrate/removed-tools-and-components.html#GUID-F182E075-858A-4468-9434-8FC1704E7BB7> ---rony On 27.01.2022 14:53, Rony G. Flatscher wrote: > On 27.01.2022 13:53, Marc Remes wrote: >> And a side note.. >> You need java 9 or above to compile and run this. >> >> Which brings up another topic : are we ready to stop supporting java 8? > Please no, unless you want to remove most of the Java installed base for NetRexx. > :) > > Seriously, NetRexx should support Java 8 as long as Java 8 gets supported by OpenJDK distributors. > E.g. Oracle and Azul support Java 8 until December 2030, for very good reasons! Actually Java 8 gets > currently a longer support than Java 11 LTS and Java 17 LTS, believe it or not. > > [BSF4ooRexx still supports Java 6 as its baseline (that is the reason for "6" in "641", "41" means > ooRexx baseline is version 4.1) as there are companies/organizations that have still Java 6 > deployed. This incurs quite some overhead and support efforts as in Java 6 one needs to use > java.lang.reflect whereas starting with Java 9 one must use java.lang.invoke instead (actually > BSF4ooRexx uses by default java.lang.invoke starting with Java 8 as Java 7, where this package got > introduced, has some missing support in that area).] > > In general a good overview of the support dates for different versions of Java by different > distributors can be found here: <https://en.wikipedia.org/wiki/Java_version_history>. > > ---rony > |
From: Rony G. F. <Ron...@wu...> - 2022-01-27 13:54:11
|
On 27.01.2022 13:53, Marc Remes wrote: > And a side note.. > You need java 9 or above to compile and run this. > > Which brings up another topic : are we ready to stop supporting java 8? Please no, unless you want to remove most of the Java installed base for NetRexx. :) Seriously, NetRexx should support Java 8 as long as Java 8 gets supported by OpenJDK distributors. E.g. Oracle and Azul support Java 8 until December 2030, for very good reasons! Actually Java 8 gets currently a longer support than Java 11 LTS and Java 17 LTS, believe it or not. [BSF4ooRexx still supports Java 6 as its baseline (that is the reason for "6" in "641", "41" means ooRexx baseline is version 4.1) as there are companies/organizations that have still Java 6 deployed. This incurs quite some overhead and support efforts as in Java 6 one needs to use java.lang.reflect whereas starting with Java 9 one must use java.lang.invoke instead (actually BSF4ooRexx uses by default java.lang.invoke starting with Java 8 as Java 7, where this package got introduced, has some missing support in that area).] In general a good overview of the support dates for different versions of Java by different distributors can be found here: <https://en.wikipedia.org/wiki/Java_version_history>. ---rony |
From: Marc R. <re...@gm...> - 2022-01-27 12:53:17
|
And a side note.. You need java 9 or above to compile and run this. Which brings up another topic : are we ready to stop supporting java 8? Marc On 1/27/22 13:24, Marc Remes wrote: > L.S., > > I pushed a new version of RxJrt.nrx on the new issues/4-modules branch. > Any module jar file found on the paths provided in --add-modules will be reported. > > You need to load any extra modules not included in the run-time jrt:/ as follows: > Either set JDK_JAVA_OPTIONS environment variable (note the semi-colon vs colon) > On linux,mac : export JDK_JAVA_OPTIONS='--module-path path1:path2' > On windows : set JDK_JAVA_OPTIONS="--module-path path1;path2" > and then nrc -run RxJrt (or java RxJrt) > > Or java --module-path path1:path2 RxJrt > > Note, NetRexx does not yet load classes from extra modules, this is just preliminary work.. > > Marc > > > _______________________________________________ > Netrexx-develop mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/netrexx-develop |
From: Marc R. <re...@gm...> - 2022-01-27 12:40:49
|
L.S., I pushed a new version of RxJrt.nrx on the new issues/4-modules branch. Any module jar file found on the paths provided in --add-modules will be reported. You need to load any extra modules not included in the run-time jrt:/ as follows: Either set JDK_JAVA_OPTIONS environment variable (note the semi-colon vs colon) On linux,mac : export JDK_JAVA_OPTIONS='--module-path path1:path2' On windows : set JDK_JAVA_OPTIONS="--module-path path1;path2" and then nrc -run RxJrt (or java RxJrt) Or java --module-path path1:path2 RxJrt Note, NetRexx does not yet load classes from extra modules, this is just preliminary work.. Marc |
From: René J. <rvj...@xs...> - 2022-01-26 17:56:58
|
Dear developers, The remnants of the Kenai issue list are now visible at https://github.com/RexxLA/NetRexx/issues <https://github.com/RexxLA/NetRexx/issues> , with some new ones added. Please feel free to add your own, comment, branch to implement a solution, etc. Best regards, René. |
From: René J. <rvj...@xs...> - 2022-01-26 15:01:59
|
Hi Terry, I can confirm that this is a bug (of the kind of: expected functionality not available). As the same thing goes for 4.01, it has no consequence for the 4.02 release. It means that while the problem is looked at, JDK 8 is indicated for JavaFX and NetRexx. We will try to solve the problem of using Java modules from other packages, as opposed to those delivered in the JDK's =>9, as soon as possible. Thanks for uncovering this. Best regards, René. > On 25 Jan 2022, at 08:38, Terry Fuller <ta...@pg...> wrote: > > Hello René, > > Trying out netrexx 4.02: > > on Linux Mint 20.2 (debian distro) > with java 11 (!) [openjdk 11.0.13 2021-10-19 > OpenJDK Runtime Environment (build 11.0.13+8-Ubuntu- 0ubuntu1.20.04) > OpenJDK 64-Bit Server VM (build 11.0.13+8-Ubuntu-0ubuntu1.20.04, mixed mode, sharing)} > I got thru the basic install checks. Now I'm working my way thru the examples, I was able to compile and run rexxcps and testdate. But when I try to compile TreeViewSampleNRX I get the following: > > NetRexx portable processor 4.02-GA build 55-20220124-1319 > Copyright (c) RexxLA, 2011,2022. All rights reserved. > Parts Copyright (c) IBM Corporation, 1995,2008. > Program TreeViewSampleNRX.nrx > 10 +++ import javafx.collections. > +++ ^^^^^^ > +++ Warning: No classes found for import from package 'javafx.collections.' > 16 +++ class TreeViewSampleNRX extends Application > +++ ^^^^^^^^^^^ > +++ Error: The class 'Application' cannot be found > Compilation of 'TreeViewSampleNRX.nrx' failed [one error, one warning] > > > I've installed both the OpenJava JDK and javafx (tho' I don't know how to verify that). In the olden days I used to be able to use the javadoc documentation to root around in the classes, but I cannot seem to find that now (after lots of googling/duckduckgo'ing). If you've got a pointer to javadoc for version 11, I might be able to limp along a little further 😉 > > On 2022-01-24 03:50, René Jansen wrote: >> Dear developers, >> >> I am releasing 4.02 today as an (not marked as such) release candidate. This because there is some work to be done that will disrupt the opportunity to release 4.02 with a limited change set. >> It contains the improvements as signalled in the release notes: >> >> NetRexx 4.02 GA [Januari 24, 2022] >> >> - for building NetRexx 4.0.2, Java 8 is now the lowest supported version >> - tested and buildable from Java 8 up to and including Java 19ea >> - including a fix for building on Java >=18 >> - NetRexx option (no)annotate to turn off pass through annotations >> - NetRexxC.jar and NetRexxF.jar now contain the ANT task for NetRexx >> - The ANT task is modified for the new -annotations option >> - The ANT task is modified for the new -address option >> - ANT in the source code repository upgraded to 1.10 for building NetRexx >> - a new chapter in the Programming Guide documenting two ANT scenarios >> - new special word asknoecho to request console input without echo, e.g. for passwords >> - NetRexx option MOD for generation of tailored source representations (Jason Martin) >> - documentation additions and corrections (numerous) >> - the base font for all documents is now an open source version of Times, due to font copyright issues >> >> Pipeline additions, improvements: >> - fix for arguments on command stage >> - DIGEST stage (SHA1, SHA256, SHA512, MD2, MD5 and more). >> - a small CMS-compatibility improvement for stage LITERAL (Jeff Hennick) >> - a new pipr script that is guaranteed to work in a Docker container (Marc Remes) >> >> Releasing it as a RC first leaves us with the option of recalling it when accidents happen, or do nothing when it is fine. It does not seem to contain high-risk issues like 4.01 - and that was very successful. >> It will hit the website sometimes later today CET. >> >> For NetRexx 5 I would like to focus on: >> >> - solving the issue with output handles and multithreading that inhibits a well working JSR223 interface (René/Marc) >> - a Streams implementation (closely related with the previous issue at the core, but also delivering a Classic Rexx compatible I/O model) (René/Marc) >> - address enhancements (address with etc, integration with the OS Address package, outtrap): (Marc/René) >> - CMS compatibility enhancements (if necessary; up to Jeff) >> - command line versus .njp versus conformity (René) >> - Android introduction, builds and examples (a lot, if not most work already done by Jason) >> - fixing an issue with Annotations that is there but nobody noticed >> >> I announced the move to Github at the 2021 Symposium, but it is not so bad as it sounds: the main repo will be at SourceForge for the time being, but I will maintain a shadow repo at Github. The issue list, however, will be at Github (we never got around to use the one at SourceForge, so I will use all the project/issue/kanban/discussion fora infra at Github. Thanks to Jason we have the complete list of open issues from when we needed to move away from project Kenai. >> >> Please let me know your Github userid if I don’t know them yet. The ownership of the Github repo is with the RexxLA user, but I will mostly use my personal userid to do the work. If you are reading this list and are a ‘management/continuity’-user of the SF NetRexx repository, please be in touch to continue in this role, if you still want to do that. >> >> Best regards, >> >> René. >> >> >> >> >> _______________________________________________ >> Netrexx-develop mailing list >> Net...@li... <mailto:Net...@li...> >> https://lists.sourceforge.net/lists/listinfo/netrexx-develop <https://lists.sourceforge.net/lists/listinfo/netrexx-develop> > -- > taf > _______________________________________________ > Netrexx-develop mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/netrexx-develop |
From: Rony G. F. <Ron...@wu...> - 2022-01-25 13:14:44
|
One maybe helpful pointer: here are the slides for my lecture "Business Programming 2 (BP2)" at a Business university for students who may not have had any programming skills when they started with BP1. BP2 is about using and taking advantage of Java (without a need to learn Java programming at all!) using the programming language ooRexx with the external function package BSF4ooRexx which bridges ooRexx and Java. Here are the slides: <https://wi.wu.ac.at/rgf/wu/lehre/autojava/material/foils/>, which usually also teach the principles that get exploited (like socket programming, GUI programming, XML parsing etc.). The slides in "AutoJava-BSF4ooRexx-08-Environment.pdf" got created to teach and to document how to create "manually" a Java runtime/development environment that also includes JavaFX and any other Java modules, no matter where they come from. The examples for adding the JavaFX modules manually are given for Windows and Unix step by step. However, having installation packages for OpenJDK and OpenJDK+FX, I would suggest to download OpenJDK+FX which also signals to the distributors the need for these four modules. HTH, ---rony On 25.01.2022 13:27, Rony G. Flatscher wrote: > > Hi, > > with Java 11 the four JavaFX modules got removed from the standard OpenJDK installation package. > > However, as OpenJDK built on the same source allows for different companies and people to create > their own distributions, there are plenty of possibilities to download "Java-Full" or "Java FX" > installation packages. Just watch out for the package that includes JavaFX. > > Some links: > > Liberica: <https://bell-sw.com/pages/downloads/#mn>, pick "Package" and choice either "Full > JDK" or "Full JRE" > > Zulu: <https://www.azul.com/downloads/?package=jdk>, pick "Java Package" and choice either > "JDK FX" or "JRE FX" > > where "JDK" stands for "Java development kit" and "JRE" stands for "Java runtime environment". I > would advise to pick the JDK versions with FX as in today's client world there is enough space > available. > > BTW, be careful about Oracle's version as Oracle has changed their license (they own all rights on > Java and can therefore assign any license to their distribution) such that commercial use is not > free. The OpenJDK distributions (same code base) however are free and use the license "GPL with > classpath exception". > > There are other OpenJDK distributors including Amazon, IBM, (believe it or not) Microsoft, SAP, > and many more. > > HTH, > > ---rony > > > On 25.01.2022 09:34, René Jansen wrote: >> Hi Terry, >> >> This is correct and expected. JavaFX is not part of any standard Java install, so you will need >> to download this before this example runs correctly. I will make a note of that and document that >> in the next release. >> The JavaFX toolkit is to be gotten at https://openjfx.io <https://openjfx.io> - did not try this >> yet myself. >> >> Best regards, >> >> René. >> >> >> >>> On 25 Jan 2022, at 08:38, Terry Fuller <ta...@pg... <mailto:ta...@pg...>> wrote: >>> >>> Hello René, >>> >>> Trying out netrexx 4.02: >>> >>> * on Linux Mint 20.2 (debian distro) >>> * with java 11 (!) [openjdk 11.0.13 2021-10-19 >>> OpenJDK Runtime Environment (build 11.0.13+8-Ubuntu- 0ubuntu1.20.04) >>> OpenJDK 64-Bit Server VM (build 11.0.13+8-Ubuntu-0ubuntu1.20.04, >>> mixed mode, sharing)} >>> >>> I got thru the basic install checks. Now I'm working my way thru the examples, I was able to >>> compile and run rexxcps and testdate. But when I try to compile TreeViewSampleNRX I get the >>> following: >>> >>> NetRexx portable processor 4.02-GA build 55-20220124-1319 Copyright (c) RexxLA, 2011,2022. All >>> rights reserved. Parts Copyright (c) IBM Corporation, 1995,2008. Program TreeViewSampleNRX.nrx >>> 10 +++ import javafx.collections. +++ ^^^^^^ +++ Warning: No classes found for import from >>> package 'javafx.collections.' 16 +++ class TreeViewSampleNRX extends Application +++ ^^^^^^^^^^^ >>> +++ Error: The class 'Application' cannot be found Compilation of 'TreeViewSampleNRX.nrx' failed >>> [one error, one warning] >>> >>> I've installed both the OpenJava JDK and javafx (tho' I don't know how to verify that). In the >>> olden days I used to be able to use the javadoc documentation to root around in the classes, but >>> I cannot seem to find that now (after lots of googling/duckduckgo'ing). If you've got a pointer >>> to javadoc for version 11, I might be able to limp along a little further 😉 >>> >>> On 2022-01-24 03:50, René Jansen wrote: >>>> Dear developers, >>>> >>>> I am releasing 4.02 today as an (not marked as such) release candidate. This because there is some work to be done that will disrupt the opportunity to release 4.02 with a limited change set. >>>> It contains the improvements as signalled in the release notes: >>>> >>>> NetRexx 4.02 GA [Januari 24, 2022] >>>> >>>> - for building NetRexx 4.0.2, Java 8 is now the lowest supported version >>>> - tested and buildable from Java 8 up to and including Java 19ea >>>> - including a fix for building on Java >=18 >>>> - NetRexx option (no)annotate to turn off pass through annotations >>>> - NetRexxC.jar and NetRexxF.jar now contain the ANT task for NetRexx >>>> - The ANT task is modified for the new -annotations option >>>> - The ANT task is modified for the new -address option >>>> - ANT in the source code repository upgraded to 1.10 for building NetRexx >>>> - a new chapter in the Programming Guide documenting two ANT scenarios >>>> - new special word asknoecho to request console input without echo, e.g. for passwords >>>> - NetRexx option MOD for generation of tailored source representations (Jason Martin) >>>> - documentation additions and corrections (numerous) >>>> - the base font for all documents is now an open source version of Times, due to font copyright issues >>>> >>>> Pipeline additions, improvements: >>>> - fix for arguments on command stage >>>> - DIGEST stage (SHA1, SHA256, SHA512, MD2, MD5 and more). >>>> - a small CMS-compatibility improvement for stage LITERAL (Jeff Hennick) >>>> - a new pipr script that is guaranteed to work in a Docker container (Marc Remes) >>>> >>>> Releasing it as a RC first leaves us with the option of recalling it when accidents happen, or do nothing when it is fine. It does not seem to contain high-risk issues like 4.01 - and that was very successful. >>>> It will hit the website sometimes later today CET. >>>> >>>> For NetRexx 5 I would like to focus on: >>>> >>>> - solving the issue with output handles and multithreading that inhibits a well working JSR223 interface (René/Marc) >>>> - a Streams implementation (closely related with the previous issue at the core, but also delivering a Classic Rexx compatible I/O model) (René/Marc) >>>> - address enhancements (address with etc, integration with the OS Address package, outtrap): (Marc/René) >>>> - CMS compatibility enhancements (if necessary; up to Jeff) >>>> - command line versus .njp versus conformity (René) >>>> - Android introduction, builds and examples (a lot, if not most work already done by Jason) >>>> - fixing an issue with Annotations that is there but nobody noticed >>>> >>>> I announced the move to Github at the 2021 Symposium, but it is not so bad as it sounds: the main repo will be at SourceForge for the time being, but I will maintain a shadow repo at Github. The issue list, however, will be at Github (we never got around to use the one at SourceForge, so I will use all the project/issue/kanban/discussion fora infra at Github. Thanks to Jason we have the complete list of open issues from when we needed to move away from project Kenai. >>>> >>>> Please let me know your Github userid if I don’t know them yet. The ownership of the Github repo is with the RexxLA user, but I will mostly use my personal userid to do the work. If you are reading this list and are a ‘management/continuity’-user of the SF NetRexx repository, please be in touch to continue in this role, if you still want to do that. >>>> >>>> Best regards, >>>> >>>> René. >>>> |
From: René J. <rvj...@xs...> - 2022-01-25 12:41:54
|
Hi Terry, Java 8 is fine. For 9 and later, it is the JPMS - Java Modules Brave New World. I am looking into it today. Best regards, René > On 25 Jan 2022, at 09:34, René Jansen <rvj...@xs...> wrote: > > Hi Terry, > > This is correct and expected. JavaFX is not part of any standard Java install, so you will need to download this before this example runs correctly. I will make a note of that and document that in the next release. > The JavaFX toolkit is to be gotten at https://openjfx.io <https://openjfx.io/> - did not try this yet myself. > > Best regards, > > René. > > > >> On 25 Jan 2022, at 08:38, Terry Fuller <ta...@pg... <mailto:ta...@pg...>> wrote: >> >> Hello René, >> >> Trying out netrexx 4.02: >> >> on Linux Mint 20.2 (debian distro) >> with java 11 (!) [openjdk 11.0.13 2021-10-19 >> OpenJDK Runtime Environment (build 11.0.13+8-Ubuntu- 0ubuntu1.20.04) >> OpenJDK 64-Bit Server VM (build 11.0.13+8-Ubuntu-0ubuntu1.20.04, mixed mode, sharing)} >> I got thru the basic install checks. Now I'm working my way thru the examples, I was able to compile and run rexxcps and testdate. But when I try to compile TreeViewSampleNRX I get the following: >> >> NetRexx portable processor 4.02-GA build 55-20220124-1319 >> Copyright (c) RexxLA, 2011,2022. All rights reserved. >> Parts Copyright (c) IBM Corporation, 1995,2008. >> Program TreeViewSampleNRX.nrx >> 10 +++ import javafx.collections. >> +++ ^^^^^^ >> +++ Warning: No classes found for import from package 'javafx.collections.' >> 16 +++ class TreeViewSampleNRX extends Application >> +++ ^^^^^^^^^^^ >> +++ Error: The class 'Application' cannot be found >> Compilation of 'TreeViewSampleNRX.nrx' failed [one error, one warning] >> >> >> I've installed both the OpenJava JDK and javafx (tho' I don't know how to verify that). In the olden days I used to be able to use the javadoc documentation to root around in the classes, but I cannot seem to find that now (after lots of googling/duckduckgo'ing). If you've got a pointer to javadoc for version 11, I might be able to limp along a little further 😉 >> >> On 2022-01-24 03:50, René Jansen wrote: >>> Dear developers, >>> >>> I am releasing 4.02 today as an (not marked as such) release candidate. This because there is some work to be done that will disrupt the opportunity to release 4.02 with a limited change set. >>> It contains the improvements as signalled in the release notes: >>> >>> NetRexx 4.02 GA [Januari 24, 2022] >>> >>> - for building NetRexx 4.0.2, Java 8 is now the lowest supported version >>> - tested and buildable from Java 8 up to and including Java 19ea >>> - including a fix for building on Java >=18 >>> - NetRexx option (no)annotate to turn off pass through annotations >>> - NetRexxC.jar and NetRexxF.jar now contain the ANT task for NetRexx >>> - The ANT task is modified for the new -annotations option >>> - The ANT task is modified for the new -address option >>> - ANT in the source code repository upgraded to 1.10 for building NetRexx >>> - a new chapter in the Programming Guide documenting two ANT scenarios >>> - new special word asknoecho to request console input without echo, e.g. for passwords >>> - NetRexx option MOD for generation of tailored source representations (Jason Martin) >>> - documentation additions and corrections (numerous) >>> - the base font for all documents is now an open source version of Times, due to font copyright issues >>> >>> Pipeline additions, improvements: >>> - fix for arguments on command stage >>> - DIGEST stage (SHA1, SHA256, SHA512, MD2, MD5 and more). >>> - a small CMS-compatibility improvement for stage LITERAL (Jeff Hennick) >>> - a new pipr script that is guaranteed to work in a Docker container (Marc Remes) >>> >>> Releasing it as a RC first leaves us with the option of recalling it when accidents happen, or do nothing when it is fine. It does not seem to contain high-risk issues like 4.01 - and that was very successful. >>> It will hit the website sometimes later today CET. >>> >>> For NetRexx 5 I would like to focus on: >>> >>> - solving the issue with output handles and multithreading that inhibits a well working JSR223 interface (René/Marc) >>> - a Streams implementation (closely related with the previous issue at the core, but also delivering a Classic Rexx compatible I/O model) (René/Marc) >>> - address enhancements (address with etc, integration with the OS Address package, outtrap): (Marc/René) >>> - CMS compatibility enhancements (if necessary; up to Jeff) >>> - command line versus .njp versus conformity (René) >>> - Android introduction, builds and examples (a lot, if not most work already done by Jason) >>> - fixing an issue with Annotations that is there but nobody noticed >>> >>> I announced the move to Github at the 2021 Symposium, but it is not so bad as it sounds: the main repo will be at SourceForge for the time being, but I will maintain a shadow repo at Github. The issue list, however, will be at Github (we never got around to use the one at SourceForge, so I will use all the project/issue/kanban/discussion fora infra at Github. Thanks to Jason we have the complete list of open issues from when we needed to move away from project Kenai. >>> >>> Please let me know your Github userid if I don’t know them yet. The ownership of the Github repo is with the RexxLA user, but I will mostly use my personal userid to do the work. If you are reading this list and are a ‘management/continuity’-user of the SF NetRexx repository, please be in touch to continue in this role, if you still want to do that. >>> >>> Best regards, >>> >>> René. >>> >>> >>> >>> >>> _______________________________________________ >>> Netrexx-develop mailing list >>> Net...@li... <mailto:Net...@li...> >>> https://lists.sourceforge.net/lists/listinfo/netrexx-develop <https://lists.sourceforge.net/lists/listinfo/netrexx-develop> >> -- >> taf >> _______________________________________________ >> Netrexx-develop mailing list >> Net...@li... <mailto:Net...@li...> >> https://lists.sourceforge.net/lists/listinfo/netrexx-develop > > _______________________________________________ > Netrexx-develop mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/netrexx-develop |
From: Rony G. F. <Ron...@wu...> - 2022-01-25 12:28:02
|
Hi, with Java 11 the four JavaFX modules got removed from the standard OpenJDK installation package. However, as OpenJDK built on the same source allows for different companies and people to create their own distributions, there are plenty of possibilities to download "Java-Full" or "Java FX" installation packages. Just watch out for the package that includes JavaFX. Some links: Liberica: <https://bell-sw.com/pages/downloads/#mn>, pick "Package" and choice either "Full JDK" or "Full JRE" Zulu: <https://www.azul.com/downloads/?package=jdk>, pick "Java Package" and choice either "JDK FX" or "JRE FX" where "JDK" stands for "Java development kit" and "JRE" stands for "Java runtime environment". I would advise to pick the JDK versions with FX as in today's client world there is enough space available. BTW, be careful about Oracle's version as Oracle has changed their license (they own all rights on Java and can therefore assign any license to their distribution) such that commercial use is not free. The OpenJDK distributions (same code base) however are free and use the license "GPL with classpath exception". There are other OpenJDK distributors including Amazon, IBM, (believe it or not) Microsoft, SAP, and many more. HTH, ---rony On 25.01.2022 09:34, René Jansen wrote: > Hi Terry, > > This is correct and expected. JavaFX is not part of any standard Java install, so you will need to > download this before this example runs correctly. I will make a note of that and document that in > the next release. > The JavaFX toolkit is to be gotten at https://openjfx.io <https://openjfx.io> - did not try this > yet myself. > > Best regards, > > René. > > > >> On 25 Jan 2022, at 08:38, Terry Fuller <ta...@pg... <mailto:ta...@pg...>> wrote: >> >> Hello René, >> >> Trying out netrexx 4.02: >> >> * on Linux Mint 20.2 (debian distro) >> * with java 11 (!) [openjdk 11.0.13 2021-10-19 >> OpenJDK Runtime Environment (build 11.0.13+8-Ubuntu- 0ubuntu1.20.04) >> OpenJDK 64-Bit Server VM (build 11.0.13+8-Ubuntu-0ubuntu1.20.04, >> mixed mode, sharing)} >> >> I got thru the basic install checks. Now I'm working my way thru the examples, I was able to >> compile and run rexxcps and testdate. But when I try to compile TreeViewSampleNRX I get the >> following: >> >> NetRexx portable processor 4.02-GA build 55-20220124-1319 Copyright (c) RexxLA, 2011,2022. All >> rights reserved. Parts Copyright (c) IBM Corporation, 1995,2008. Program TreeViewSampleNRX.nrx 10 >> +++ import javafx.collections. +++ ^^^^^^ +++ Warning: No classes found for import from package >> 'javafx.collections.' 16 +++ class TreeViewSampleNRX extends Application +++ ^^^^^^^^^^^ +++ >> Error: The class 'Application' cannot be found Compilation of 'TreeViewSampleNRX.nrx' failed [one >> error, one warning] >> >> I've installed both the OpenJava JDK and javafx (tho' I don't know how to verify that). In the >> olden days I used to be able to use the javadoc documentation to root around in the classes, but >> I cannot seem to find that now (after lots of googling/duckduckgo'ing). If you've got a pointer >> to javadoc for version 11, I might be able to limp along a little further 😉 >> >> On 2022-01-24 03:50, René Jansen wrote: >>> Dear developers, >>> >>> I am releasing 4.02 today as an (not marked as such) release candidate. This because there is some work to be done that will disrupt the opportunity to release 4.02 with a limited change set. >>> It contains the improvements as signalled in the release notes: >>> >>> NetRexx 4.02 GA [Januari 24, 2022] >>> >>> - for building NetRexx 4.0.2, Java 8 is now the lowest supported version >>> - tested and buildable from Java 8 up to and including Java 19ea >>> - including a fix for building on Java >=18 >>> - NetRexx option (no)annotate to turn off pass through annotations >>> - NetRexxC.jar and NetRexxF.jar now contain the ANT task for NetRexx >>> - The ANT task is modified for the new -annotations option >>> - The ANT task is modified for the new -address option >>> - ANT in the source code repository upgraded to 1.10 for building NetRexx >>> - a new chapter in the Programming Guide documenting two ANT scenarios >>> - new special word asknoecho to request console input without echo, e.g. for passwords >>> - NetRexx option MOD for generation of tailored source representations (Jason Martin) >>> - documentation additions and corrections (numerous) >>> - the base font for all documents is now an open source version of Times, due to font copyright issues >>> >>> Pipeline additions, improvements: >>> - fix for arguments on command stage >>> - DIGEST stage (SHA1, SHA256, SHA512, MD2, MD5 and more). >>> - a small CMS-compatibility improvement for stage LITERAL (Jeff Hennick) >>> - a new pipr script that is guaranteed to work in a Docker container (Marc Remes) >>> >>> Releasing it as a RC first leaves us with the option of recalling it when accidents happen, or do nothing when it is fine. It does not seem to contain high-risk issues like 4.01 - and that was very successful. >>> It will hit the website sometimes later today CET. >>> >>> For NetRexx 5 I would like to focus on: >>> >>> - solving the issue with output handles and multithreading that inhibits a well working JSR223 interface (René/Marc) >>> - a Streams implementation (closely related with the previous issue at the core, but also delivering a Classic Rexx compatible I/O model) (René/Marc) >>> - address enhancements (address with etc, integration with the OS Address package, outtrap): (Marc/René) >>> - CMS compatibility enhancements (if necessary; up to Jeff) >>> - command line versus .njp versus conformity (René) >>> - Android introduction, builds and examples (a lot, if not most work already done by Jason) >>> - fixing an issue with Annotations that is there but nobody noticed >>> >>> I announced the move to Github at the 2021 Symposium, but it is not so bad as it sounds: the main repo will be at SourceForge for the time being, but I will maintain a shadow repo at Github. The issue list, however, will be at Github (we never got around to use the one at SourceForge, so I will use all the project/issue/kanban/discussion fora infra at Github. Thanks to Jason we have the complete list of open issues from when we needed to move away from project Kenai. >>> >>> Please let me know your Github userid if I don’t know them yet. The ownership of the Github repo is with the RexxLA user, but I will mostly use my personal userid to do the work. If you are reading this list and are a ‘management/continuity’-user of the SF NetRexx repository, please be in touch to continue in this role, if you still want to do that. >>> >>> Best regards, >>> >>> René. >>> >>> |
From: René J. <rvj...@xs...> - 2022-01-25 08:34:26
|
Hi Terry, This is correct and expected. JavaFX is not part of any standard Java install, so you will need to download this before this example runs correctly. I will make a note of that and document that in the next release. The JavaFX toolkit is to be gotten at https://openjfx.io <https://openjfx.io/> - did not try this yet myself. Best regards, René. > On 25 Jan 2022, at 08:38, Terry Fuller <ta...@pg...> wrote: > > Hello René, > > Trying out netrexx 4.02: > > on Linux Mint 20.2 (debian distro) > with java 11 (!) [openjdk 11.0.13 2021-10-19 > OpenJDK Runtime Environment (build 11.0.13+8-Ubuntu- 0ubuntu1.20.04) > OpenJDK 64-Bit Server VM (build 11.0.13+8-Ubuntu-0ubuntu1.20.04, mixed mode, sharing)} > I got thru the basic install checks. Now I'm working my way thru the examples, I was able to compile and run rexxcps and testdate. But when I try to compile TreeViewSampleNRX I get the following: > > NetRexx portable processor 4.02-GA build 55-20220124-1319 > Copyright (c) RexxLA, 2011,2022. All rights reserved. > Parts Copyright (c) IBM Corporation, 1995,2008. > Program TreeViewSampleNRX.nrx > 10 +++ import javafx.collections. > +++ ^^^^^^ > +++ Warning: No classes found for import from package 'javafx.collections.' > 16 +++ class TreeViewSampleNRX extends Application > +++ ^^^^^^^^^^^ > +++ Error: The class 'Application' cannot be found > Compilation of 'TreeViewSampleNRX.nrx' failed [one error, one warning] > > > I've installed both the OpenJava JDK and javafx (tho' I don't know how to verify that). In the olden days I used to be able to use the javadoc documentation to root around in the classes, but I cannot seem to find that now (after lots of googling/duckduckgo'ing). If you've got a pointer to javadoc for version 11, I might be able to limp along a little further 😉 > > On 2022-01-24 03:50, René Jansen wrote: >> Dear developers, >> >> I am releasing 4.02 today as an (not marked as such) release candidate. This because there is some work to be done that will disrupt the opportunity to release 4.02 with a limited change set. >> It contains the improvements as signalled in the release notes: >> >> NetRexx 4.02 GA [Januari 24, 2022] >> >> - for building NetRexx 4.0.2, Java 8 is now the lowest supported version >> - tested and buildable from Java 8 up to and including Java 19ea >> - including a fix for building on Java >=18 >> - NetRexx option (no)annotate to turn off pass through annotations >> - NetRexxC.jar and NetRexxF.jar now contain the ANT task for NetRexx >> - The ANT task is modified for the new -annotations option >> - The ANT task is modified for the new -address option >> - ANT in the source code repository upgraded to 1.10 for building NetRexx >> - a new chapter in the Programming Guide documenting two ANT scenarios >> - new special word asknoecho to request console input without echo, e.g. for passwords >> - NetRexx option MOD for generation of tailored source representations (Jason Martin) >> - documentation additions and corrections (numerous) >> - the base font for all documents is now an open source version of Times, due to font copyright issues >> >> Pipeline additions, improvements: >> - fix for arguments on command stage >> - DIGEST stage (SHA1, SHA256, SHA512, MD2, MD5 and more). >> - a small CMS-compatibility improvement for stage LITERAL (Jeff Hennick) >> - a new pipr script that is guaranteed to work in a Docker container (Marc Remes) >> >> Releasing it as a RC first leaves us with the option of recalling it when accidents happen, or do nothing when it is fine. It does not seem to contain high-risk issues like 4.01 - and that was very successful. >> It will hit the website sometimes later today CET. >> >> For NetRexx 5 I would like to focus on: >> >> - solving the issue with output handles and multithreading that inhibits a well working JSR223 interface (René/Marc) >> - a Streams implementation (closely related with the previous issue at the core, but also delivering a Classic Rexx compatible I/O model) (René/Marc) >> - address enhancements (address with etc, integration with the OS Address package, outtrap): (Marc/René) >> - CMS compatibility enhancements (if necessary; up to Jeff) >> - command line versus .njp versus conformity (René) >> - Android introduction, builds and examples (a lot, if not most work already done by Jason) >> - fixing an issue with Annotations that is there but nobody noticed >> >> I announced the move to Github at the 2021 Symposium, but it is not so bad as it sounds: the main repo will be at SourceForge for the time being, but I will maintain a shadow repo at Github. The issue list, however, will be at Github (we never got around to use the one at SourceForge, so I will use all the project/issue/kanban/discussion fora infra at Github. Thanks to Jason we have the complete list of open issues from when we needed to move away from project Kenai. >> >> Please let me know your Github userid if I don’t know them yet. The ownership of the Github repo is with the RexxLA user, but I will mostly use my personal userid to do the work. If you are reading this list and are a ‘management/continuity’-user of the SF NetRexx repository, please be in touch to continue in this role, if you still want to do that. >> >> Best regards, >> >> René. >> >> >> >> >> _______________________________________________ >> Netrexx-develop mailing list >> Net...@li... <mailto:Net...@li...> >> https://lists.sourceforge.net/lists/listinfo/netrexx-develop <https://lists.sourceforge.net/lists/listinfo/netrexx-develop> > -- > taf > _______________________________________________ > Netrexx-develop mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/netrexx-develop |
From: Terry F. <ta...@pg...> - 2022-01-25 07:51:19
|
Hello René, Trying out netrexx 4.02: * on Linux Mint 20.2 (debian distro) * with java 11 (!) [openjdk 11.0.13 2021-10-19 OpenJDK Runtime Environment (build 11.0.13+8-Ubuntu- 0ubuntu1.20.04) OpenJDK 64-Bit Server VM (build 11.0.13+8-Ubuntu-0ubuntu1.20.04, mixed mode, sharing)} I got thru the basic install checks. Now I'm working my way thru the examples, I was able to compile and run rexxcps and testdate. But when I try to compile TreeViewSampleNRX I get the following: NetRexx portable processor 4.02-GA build 55-20220124-1319 Copyright (c) RexxLA, 2011,2022. All rights reserved. Parts Copyright (c) IBM Corporation, 1995,2008. Program TreeViewSampleNRX.nrx 10 +++ import javafx.collections. +++ ^^^^^^ +++ Warning: No classes found for import from package 'javafx.collections.' 16 +++ class TreeViewSampleNRX extends Application +++ ^^^^^^^^^^^ +++ Error: The class 'Application' cannot be found Compilation of 'TreeViewSampleNRX.nrx' failed [one error, one warning] I've installed both the OpenJava JDK and javafx (tho' I don't know how to verify that). In the olden days I used to be able to use the javadoc documentation to root around in the classes, but I cannot seem to find that now (after lots of googling/duckduckgo'ing). If you've got a pointer to javadoc for version 11, I might be able to limp along a little further 😉 On 2022-01-24 03:50, René Jansen wrote: > Dear developers, > > I am releasing 4.02 today as an (not marked as such) release candidate. This because there is some work to be done that will disrupt the opportunity to release 4.02 with a limited change set. > It contains the improvements as signalled in the release notes: > > NetRexx 4.02 GA [Januari 24, 2022] > > - for building NetRexx 4.0.2, Java 8 is now the lowest supported version > - tested and buildable from Java 8 up to and including Java 19ea > - including a fix for building on Java >=18 > - NetRexx option (no)annotate to turn off pass through annotations > - NetRexxC.jar and NetRexxF.jar now contain the ANT task for NetRexx > - The ANT task is modified for the new -annotations option > - The ANT task is modified for the new -address option > - ANT in the source code repository upgraded to 1.10 for building NetRexx > - a new chapter in the Programming Guide documenting two ANT scenarios > - new special word asknoecho to request console input without echo, e.g. for passwords > - NetRexx option MOD for generation of tailored source representations (Jason Martin) > - documentation additions and corrections (numerous) > - the base font for all documents is now an open source version of Times, due to font copyright issues > > Pipeline additions, improvements: > - fix for arguments on command stage > - DIGEST stage (SHA1, SHA256, SHA512, MD2, MD5 and more). > - a small CMS-compatibility improvement for stage LITERAL (Jeff Hennick) > - a new pipr script that is guaranteed to work in a Docker container (Marc Remes) > > Releasing it as a RC first leaves us with the option of recalling it when accidents happen, or do nothing when it is fine. It does not seem to contain high-risk issues like 4.01 - and that was very successful. > It will hit the website sometimes later today CET. > > For NetRexx 5 I would like to focus on: > > - solving the issue with output handles and multithreading that inhibits a well working JSR223 interface (René/Marc) > - a Streams implementation (closely related with the previous issue at the core, but also delivering a Classic Rexx compatible I/O model) (René/Marc) > - address enhancements (address with etc, integration with the OS Address package, outtrap): (Marc/René) > - CMS compatibility enhancements (if necessary; up to Jeff) > - command line versus .njp versus conformity (René) > - Android introduction, builds and examples (a lot, if not most work already done by Jason) > - fixing an issue with Annotations that is there but nobody noticed > > I announced the move to Github at the 2021 Symposium, but it is not so bad as it sounds: the main repo will be at SourceForge for the time being, but I will maintain a shadow repo at Github. The issue list, however, will be at Github (we never got around to use the one at SourceForge, so I will use all the project/issue/kanban/discussion fora infra at Github. Thanks to Jason we have the complete list of open issues from when we needed to move away from project Kenai. > > Please let me know your Github userid if I don’t know them yet. The ownership of the Github repo is with the RexxLA user, but I will mostly use my personal userid to do the work. If you are reading this list and are a ‘management/continuity’-user of the SF NetRexx repository, please be in touch to continue in this role, if you still want to do that. > > Best regards, > > René. > > > > > _______________________________________________ > Netrexx-develop mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/netrexx-develop -- taf |
From: René J. <rvj...@xs...> - 2022-01-24 21:00:37
|
As we now have a number of people possibly working on more or less breaking changes (hopefully only when they are in flight), I am personally going to start bundling my changes in feature branches; this is much easier and faster in git than it ever was in subversion and/or cvs, and it will shield us a bit against having changes ‘open’ for too long - or me spending whole nights because I broke something and wanting to fix it before you, the other developers, woke up. Which I did recently when breaking the whole thing by having Java 17 JVM classes dependent on a new ANT task that did not work - and then needing to fall back to Java 8 where the compiler did not work - long live git but I did not need the stress. This does not mean you also have to, I am only am suggesting it. If you feature branch and rebase with master now and then (better: quite often), merging will be almost painless. This has not become more important than the cooperation on the code itself, you are free to keep committing to master; only be aware that it, from NetRexx 5 on, is not the standard or preferred way of working anymore. Of course your code contributions are more appreciated than any commit/merge procedure. When observed, however, we might have more stability for working on separate issues. Best regards, René. |
From: René J. <rvj...@xs...> - 2022-01-24 11:50:50
|
Dear developers, I am releasing 4.02 today as an (not marked as such) release candidate. This because there is some work to be done that will disrupt the opportunity to release 4.02 with a limited change set. It contains the improvements as signalled in the release notes: NetRexx 4.02 GA [Januari 24, 2022] - for building NetRexx 4.0.2, Java 8 is now the lowest supported version - tested and buildable from Java 8 up to and including Java 19ea - including a fix for building on Java >=18 - NetRexx option (no)annotate to turn off pass through annotations - NetRexxC.jar and NetRexxF.jar now contain the ANT task for NetRexx - The ANT task is modified for the new -annotations option - The ANT task is modified for the new -address option - ANT in the source code repository upgraded to 1.10 for building NetRexx - a new chapter in the Programming Guide documenting two ANT scenarios - new special word asknoecho to request console input without echo, e.g. for passwords - NetRexx option MOD for generation of tailored source representations (Jason Martin) - documentation additions and corrections (numerous) - the base font for all documents is now an open source version of Times, due to font copyright issues Pipeline additions, improvements: - fix for arguments on command stage - DIGEST stage (SHA1, SHA256, SHA512, MD2, MD5 and more). - a small CMS-compatibility improvement for stage LITERAL (Jeff Hennick) - a new pipr script that is guaranteed to work in a Docker container (Marc Remes) Releasing it as a RC first leaves us with the option of recalling it when accidents happen, or do nothing when it is fine. It does not seem to contain high-risk issues like 4.01 - and that was very successful. It will hit the website sometimes later today CET. For NetRexx 5 I would like to focus on: - solving the issue with output handles and multithreading that inhibits a well working JSR223 interface (René/Marc) - a Streams implementation (closely related with the previous issue at the core, but also delivering a Classic Rexx compatible I/O model) (René/Marc) - address enhancements (address with etc, integration with the OS Address package, outtrap): (Marc/René) - CMS compatibility enhancements (if necessary; up to Jeff) - command line versus .njp versus conformity (René) - Android introduction, builds and examples (a lot, if not most work already done by Jason) - fixing an issue with Annotations that is there but nobody noticed I announced the move to Github at the 2021 Symposium, but it is not so bad as it sounds: the main repo will be at SourceForge for the time being, but I will maintain a shadow repo at Github. The issue list, however, will be at Github (we never got around to use the one at SourceForge, so I will use all the project/issue/kanban/discussion fora infra at Github. Thanks to Jason we have the complete list of open issues from when we needed to move away from project Kenai. Please let me know your Github userid if I don’t know them yet. The ownership of the Github repo is with the RexxLA user, but I will mostly use my personal userid to do the work. If you are reading this list and are a ‘management/continuity’-user of the SF NetRexx repository, please be in touch to continue in this role, if you still want to do that. Best regards, René. |
From: Jason M. <agr...@gm...> - 2022-01-20 02:42:47
|
-- NetRexx 4.01-GA Language Reference -- example at top of page 54 -- changed 'foo' to null on line two -- nrc does compile it -- running it causes Exception in thread "main" java.lang.NullPointerException -- I ask because some methods can return null whether as Rexx or as Object -- should docs warn about this? x='?' x[null, 'bar']='OK' say x['foo', 'bar'] y=x['foo'] say y['bar'] |
From: René J. <rvj...@xs...> - 2022-01-06 19:19:32
|
Hi Marc, Thank you! That might well have been the case, I only use the aliases. I will try and let you know - it would be great to have that finally working. Best regards, René. > On 6 Jan 2022, at 14:30, Marc Remes <re...@gm...> wrote: > > > Hi René, > > I did a quick check on the docker issue. > I successfully built the docker image with NetRexx-401, and I'm able to run pipes. > I did exclude the the editor and regina-rexx. The latter is in testing repo on bullsey. > > Note that the pipe shell script behaves differently than the alias.. > The shell script receives the pipe content from stdin (i.e. read line) while the pipe alias gets it as an argument.. > > Running /bin/pipe without (shell) piping something to it, waits on the read line for input. > Attaching the Dockerfile > > Was this your issue? > > Marc > > << > fc38af6b351e# echo 'literal Pipelines processor loaded. | console' | pipe > Pipelines processor loaded. > fc38af6b351e# cat /bin/pipe > #/bin/sh > read line > > java org.netrexx.njpipes.pipes.runner "$line" > fc38af6b351e# alias pip="java org.netrexx.njpipes.pipes.runner" > fc38af6b351e# alias > pip='java org.netrexx.njpipes.pipes.runner' > which-command=whence > fc38af6b351e# pip 'literal Pipelines processor loaded. | console' > Pipelines processor loaded. > fc38af6b351e# > >> > > On 1/6/22 17:42, René Jansen wrote: >> 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 >> _______________________________________________ >> Netrexx-develop mailing list >> Net...@li... >> https://lists.sourceforge.net/lists/listinfo/netrexx-develop > <Dockerfile.txt> |
From: René J. <rvj...@xs...> - 2022-01-06 16:42:38
|
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 |
From: René J. <rvj...@xs...> - 2022-01-05 20:17:53
|
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é. |
From: René J. <rvj...@xs...> - 2020-12-23 16:08:18
|
For the developers and interested parties: 3.11 has been branched for release. Master branch is NetRexx 4.X, containing 4.01 beta. From this point on, you should be able to develop, build and run with JDK’s =>9. I am running, for example, with OpenJDK 17 ea, and test with 11,13,15 (Amazon Cornetto). The good news is that 4.01 still works with JDK 8, so there is no real need to switch. For committers nothing changes, except the version number. Please report any errors or suspected errors so they can be fixed. There have been a large number of changes and although a number of problems was found while testing (and fixed by Marc) it cannot be ruled out that there is more. But all in all I have great confidence in 4.01 beta and I would run it everywhere, except for very important production systems. I would recommend a clean clone to avoid any merge problems, although I did one without problems on Linux yesterday, so you can try that first. The bootstrap compiler in 4.01 is already 4.01; the first build needs to be clean, e.g. nothing in build/classes or build/lib. best regards, René. |
From: René J. <rvj...@xs...> - 2020-12-09 19:26:21
|
You might be interested in building NetRexx 4.01 alpha for testing purposes. This is a short explanation on what to do: git fetch (this pulls in remote branches) git checkout netrexx4 (this switches your local workspace to the netrexx4 branch) now build as usual. Notes: 1) building needs Java 8. The resulting compiler runs under Java 9+. I tested with openjdk 13 on macOS (Intel) and openjdk 14 on Linux Ubuntu 20.04 on ARM-64. 2) GraalVM 11 does not work yet (on any platform) 3) Some programs error out when using the NetRexx Interpreter (-exec) git checkout master will bring you back to the master branch, which is currently at NetRexx 3.11 pre-release. best regards, René. |
From: Jason M. <agr...@gm...> - 2020-10-22 21:27:16
|
NetRexx-3.09-GA/examples/pipes add_tests01.njp addpipe_tests01.njp array_tests01.njp dateconvert_tests01.njp dateconvert_tests02.njp dateconvert_tests03.njp dateconvert_tests04.njp dateconvert_tests05.njp dateconvert_tests06.njp dateconvert_tests07.njp dateconvert_tests08.njp dateconvert_tests09.njp dateconvert_tests10.njp dateconvert_tests11.njp dateconvert_tests12.njp dateconvert_tests13.njp getKeyWord_tests01.njp query_tests1.njp siptest.njp spawntest.njp tasktest.njp tcprec.njp tcpsend.njp tcptask.njp xrange_tests1.njp |
From: Jason M. <agr...@gm...> - 2020-10-22 15:30:57
|
Do all these work on other unix boxes with letter "l"? Page 17 use 1 instead of letter "l" for the others. 1 pipe command ls -laFTl | specs 42-47 1 58-* 8 | sort | console 1 pipe command ls -laFTl | specs 42-47 1 58-* 8 | specs 7-11 1 1-6 7 12-* 12 | sort | 1 pipe command ls -laFTl | specs 42-47 1 58-* 8 | specs 7-11 1 1-6 2 7 12-* 12 | locate /2019 Mar 2/ | sort | console |
From: Jason M. <agr...@gm...> - 2020-10-22 15:18:32
|
Page 16 program. You send a command into the pipeline, and get its output: 1 pipe command ls -laFTl | console -laFTl Last character should be a 1 [one] not the letter "l" |
From: Jason M. <agr...@gm...> - 2020-10-22 15:05:24
|
Page 14 Section 3.5 2nd line - shows - /emphPortrait Mode, Page 15 Section 3.6 example - line 1 - shows - pipe (lengthp) < output.lst Maybe should be? - pipe (lengthp) < length.nrx User should note file should exist in same directory It does in examples and works correctly. |
From: Jason M. <agr...@gm...> - 2020-04-03 19:31:37
|
To better explain, the function is named "nextnonblank" If the char[] is null, just catch that and return 0. |