Multiple Versions at Launch-Time

[Alan Bateman]

On 20/10/2015 14:30, Nicolai Parlog wrote:
> :
>
> One way I hoped to do this was to treat both versions as two different
> modules, i.e. renaming them and update the dependencies on them.
>
> 	App requires LibA
> 	App requires LibB_v2
> 	LibA requires LibB_v1
>
> This does not work because both modules would export the same
> packages. That's a little disappointing - I hoped it wouldn't matter
> because no module is reading from both versions.
>
Assuming it's not "requires public LibA" then I would expect you should 
be able to create a Configuration. It will fail of course if you attempt 
to instantiate that configuration with both LibB_v1 and LibB_v2 mapped 
to the same class loader and maybe that is what you are running into.

-Alan.