Replies: 2 comments
-
Yes, I think that is something Mill should support at some point. I'm not aware of any current support for it. By JPMS support I mostly assume you mean: Instead of assembly a classpath, it assembles a module path and passes things as modules? |
Beta Was this translation helpful? Give feedback.
-
I think this sounds reasonable, but I don't have experience with the java module system myself. @froderick maybe you could open an issue with a writeup of what kind of support you would expect, so we on the Mill side can see if we can implement it? |
Beta Was this translation helpful? Give feedback.
-
Hi,
I have a multi module maven project that makes use of Java modules (module-info.java) to only expose certain packages for other modules to use. The maven support is fairly automatic, maven recognizes that Java modules are in use and supplies those to the jvm when one module depends on another. It also has fallbacks for when a module depends on a jar that doesn’t define a module itself.
My question is, are there any examples of doing this same thing with mill? I found one example related to generating os-specific install packages, but nothing about managing JPMS module interdependencies.
Mill seems like an interesting way to manage a large, modular codebase. Thanks in advance for pointing me in the right direction.
Beta Was this translation helpful? Give feedback.
All reactions