Legacy mode

[Alan Bateman]

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 ?
>
> Rémi
>
I can't tell which document you are reading 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.

Hopefully this helps,

-Alan.