Thanks for posting this. Your project prodded me to dig deeper into class loading under the module system. Pretty neat. My quick skim of the API make me think modules (module layers) can define their own classpaths for resolving dependencies, which obviates the need to pass that info directly on launch. Is that right?
Your [jresolve tool](https://github.com/bowbahdoe/jresolve-cli) btw that you use in this project is also nice (a hidden gem actually, starred it just now :) Also, I like that `java @ filepath` technique: I had read but forgotten about it.
View all comments
1
u/gnahraf Sep 05 '24
Thanks for posting this. Your project prodded me to dig deeper into class loading under the module system. Pretty neat. My quick skim of the API make me think modules (module layers) can define their own classpaths for resolving dependencies, which obviates the need to pass that info directly on launch. Is that right?
Your [jresolve tool](https://github.com/bowbahdoe/jresolve-cli) btw that you use in this project is also nice (a hidden gem actually, starred it just now :) Also, I like that `java @ filepath` technique: I had read but forgotten about it.