On 04/11/2016 10:04, Jochen Theodorou wrote:
:
What I see mostly is that all the problems you have now on a per class
level, you later have on a per module level again... for example
needing two versions of the same library being active at the same
time... and the movement away from the static module descriptor to a
dynamic module loading system with layers and all kinds of shenanigans
that will bypass these efforts in the end again
I'm not sure what you mean here but reliable configuration extends to
layers of modules too. When creating the configuration for a layer then
you can't have a module M that reads two other modules (irrespective of
which layer they are in) that export the same package to M.
So what is the background to this thread, are you running into a split
package issue when trying to migrate something to modules?
-Alan
