Multiple Versions vs "Module Hell"
David M. Lloyd
david.lloyd at redhat.com
Fri Jun 19 13:17:32 UTC 2015
It really comes down to the definition of "more than one version of a
module". What is the difference between more than one version of a
module, and to different modules which happen to have very similar code
On 06/19/2015 03:38 AM, Nicolai Parlog wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> I am writing a series about Project Jigsaw and am currently
> drafting an article about the planned features[2, 3].
> One paragraph in particular made me wonder:
> "It is not necessary to support more than one version of a module
> within a single configuration."
> At first sight this looks like it would create "Module Hell" instead
> of JAR Hell because instead of multiple JARs depending on different
> versions of the same JAR, we can now have multiple modules depending
> on different versions of the same module.
> I guess this is not so but I don't really see why not. I assume
> encapsulating the dependencies is the answer but it would be great to
> have a less speculative and vague explanation. Maybe someone on this
> list can help me out?
> Thanks in advance
>  blog.codefx.org/java/dev/motivation-goals-project-jigsaw/
>  openjdk.java.net/projects/jigsaw/goals-reqs/
>  http://openjdk.java.net/projects/jigsaw/spec/reqs/02
> - --
> PGP Key:
> a blog about software development
> Free and Open Source Software for the City of Dortmund
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (MingW32)
> -----END PGP SIGNATURE-----
More information about the jigsaw-dev