Re: Weka at jdk17+

> On Oct 17, 2021, at 8:43 PM, Eibe Frank <[email protected]> wrote:
> 
> The following works for me (--add-opens needed to be used to make
> warnings or failures regarding module boundaries go away since at
> least Java 11):
> 
> C:\Users\eibe>java -version
> openjdk version "17" 2021-09-14 LTS
> OpenJDK Runtime Environment Zulu17.28+13-CA (build 17+35-LTS)
> OpenJDK 64-Bit Server VM Zulu17.28+13-CA (build 17+35-LTS, mixed mode, sharing)
> 
> C:\Users\eibe> java --add-opens java.base/java.lang=ALL-UNNAMED -jar
> "C:\Program Files\Weka-3-8-5\weka.jar"
> 
> There don't seem to be any issues regarding MTJ when running WEKA like
> this. (Note that we are maintaining our own version of MTJ's base
> library netlib-java at
> https://svn.cms.waikato.ac.nz/svn/weka/netlib-java/ now because we had
> to compile up support for Mac ARM anyway.)
> 

I noticed the error I was getting was in a Weka package manager class initialization.
It seemed that the class was considered initialized anyhow so since this was with my application running JShell I could just repeat the last action and then it worked. It seems like some of the initial modular warnings are starting to turn into errors but there may still be ways to work around them.
I have been looking a little at ND4J myself but was stuck on a compile error. Weka must of figured most of this out for wekaDeepLearning4j so it would seem a possible alternative for MTJ, with potential GPU support, and ongoing overall support. But, I still haven’t got past the build so I have a lot to figure out yet. 

_______________________________________________
Wekalist mailing list -- [email protected]
Send posts to [email protected]
To unsubscribe send an email to [email protected]
To subscribe, unsubscribe, etc., visit https://list.waikato.ac.nz/postorius/lists/wekalist.list.waikato.ac.nz
List etiquette: http://www.cs.waikato.ac.nz/~ml/weka/mailinglist_etiquette.html