On 12/23/2024 1:56 PM, David Lloyd wrote:
If I have A->B at build time, then it should be possible to use A in a run time system that has A->B->C or A->B->D or A->B->E without A having to know or care what B's dependencies are; furthermore, it should be possible for A to bring its own C or D or E without fearing conflicts with transitive dependencies of B (a big part of classical "JAR hell").
These requirements -- the ability to isolate each subtree of dependencies to an extreme degree -- go far beyond the scope of the Java module system. We have a multitude of projects in flight for 2025, such as Value Classes, Code Reflection, and improvements in AOT caching, so it's hard to see who would have the time to work on features that address these requirements.
See you all next year, Alex
