sdedic commented on PR #7253: URL: https://github.com/apache/netbeans/pull/7253#issuecomment-2047293701
For classloading in `core.network`: at some time GraalVM JDK included Javascript engine in it, it become available from the bootclasspath as well as Truffle libraries. The `libs.graalsdk.system` module addressed that by force-loading classes from the bootstrap. It is removed in @matthiasblaesing's GraalSDK update -- I need to think about that still a little, as there are older releases of GraalVM 11/17 that (still) include javascript engine. But because of potential clashes between JRE Truffle and NB-distributed Truffle/GraalJS, both libs.truffle.api and libs.graaljs explicitly hide truffle/js packages from the app classpath, so the NB modules can load their classes cleanly. In the simplified test environment, all modules are loaded from the classpath; and the `OpenIDE-Hide-Classpath-Packages` effectively hides module's own implementation from the tests classloader. I've added a `NbModuleSuite` wrapper around the tests -- but I think there's another option, to refine `OpenIDE-Hide-Classpath-Packages` to allow module-provided packages in the case the *module itself* is on the classpath. @jlahoda - have you an opinion on this ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
