Indeed you did, I was too trigger happy. Den ons 1 jan. 2025 kl 11:49 skrev Jerome Lelasseux <lelass...@yahoo.com>:
> As explained in my email I tried this too, same problem. > > > > Le mercredi 1 janvier 2025 à 11:37:40 UTC+1, Patrik Karlström < > pat...@trixon.se> a écrit : > > > You should use the latest version,14.2, of nbm-maven-plugin. > > /Patrik > > Den ons 1 jan. 2025 kl 09:57 skrev Jerome Lelasseux > <lelass...@yahoo.com.invalid>: > > Hi and happy new year to the NB devs :-) > > My maven NB platform app uses JDK17 and nbm-maven-plugin 4.8. Works fine. > > I'd like to use JDK23 with RELEASE240 cluster on my app, but I encounter > weird problems. > > I run NB24 with Adoptium JDK23 on win11. Using compiler release=23 in > parent pom. > > [ERROR] Failed to execute goal > org.apache.netbeans.utilities:nbm-maven-plugin:4.8:manifest > (default-manifest) on project xstream: Execution default-manifest of goal > org.apache.netbeans.utilities:nbm-maven-plugin:4.8:manifest failed: > Unsupported class file major version 67 > I found > https://github.com/apache/netbeans-mavenutils-nbm-maven-plugin/issues/159 > and used the fix proposed by guydaniel. > > This way I can compile the app but *when I run it it starts but I get an > empty/skeleton NB app, like my app modules are not loaded, without any > error on the log*. I checked the target which seem to contain all the > required files. What happens ? > > > Tried with release=22, same. > > > Tried upgrading nbm to 14.2, which makes the danielguy fix above no more > necessary. > But I get : > [INFO] --- nbm:14.2:manifest (default-manifest) @ yjzcreationwizard --- > [INFO] NBM Plugin generates manifest > [INFO] Private classes referenced in module: [org.jjazz.yamjjazz.YamChord] > [ERROR] Project depends on packages not accessible at runtime in module > org.jjazzlab.plugins:yamjjazz:jar:4.1.3-SNAPSHOT > > Error seems wrong to me, I checked, module yjzcreationwizard does not use > the YamChord class. It only uses classes from module yamjjazz public > packages. Workaround was to move the YamChord class to a public package, > but it's not satisfactory. > > Anyway when I run the app I get the same problem, app runs but is "empty". > > > Jerome > >
