forax at univ-mlv.fr
Sun Sep 11 11:39:17 PDT 2011
On 09/11/2011 07:38 PM, Alan Bateman wrote:
> Rémi Forax wrote:
>> Hi everybody,
>> I've found a document describing how the legacy mode works
>> so I'm able to understand if this
>> I have two libraries lib1and lib2 and an application app.
>> The application module declare a dependency to
>> the lib1 module and another to the lib2 module,
>> lib2 also declares a dependency to lib1.
>> Now, a new incompatible version of lib1 is created,
>> and the app is updated to use this new version.
>> lib2 is not updated and still use the old version.
>> So in the module repository, there are two versions
>> of lib1.
>> Is there a problem if I run my application in legacy mode ?
> I can't tell which document you are reading
oops sorry, I should have written "I've found no document" ...
> but legacy mode means running applications in the same way that they
> are run today (meaning classpaths, JAR files, etc.). There isn't any
> way to run applications installed as modules to run in legacy mode, at
> least not with making use of implementation knowledge of the module
> library layout. At some point, and to aid migration, then we'll
> probably have to add support to allow JAR files depend on modules. I
> don't think anything has been done on that.
The JDK8 will provide a legacy mode and will have private dependencies
on several libraries
that are currently repackaged by adding a package prefix (com.sun.).
Now suppose that these libraries are installed as modules,
how the JDK will avoid conflicts with versions of these libraries
provided by the application
in the classpath ?
> Hopefully this helps,
More information about the jigsaw-dev