-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Ali,
I missed that post. That is exactly what I was going for! I just
wanted to get confirmation that there isn't already a way to do this
(or something similar).
so long ... Nicolai
On 20.10.2015 21:09, Ali Ebrahimi wrote:
> Hi, I think it
Hi,
I think it would be good we able to pass layers configuration tree by some
form via config file to java launcher.
In this way layer tree can be automatically created without need to hard
coded by developer. This config file can be created by build systems or
even by developers.
I sent this idea
Hi Nicolai,
On Tue, Oct 20, 2015 at 9:56 AM, Nicolai Parlog wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi Eric.
>
> > Why not use OSGi? Or is that what you mean by a "container"?
> I assume that the quote I gave uses "container" to mean systems like
> OSGi (it's from Alan, m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Alan,
thanks for taking the time to respond.
> Assuming it's not "requires public LibA" then I would expect you
> should be able to create a Configuration.
I am able to create a java.lang.module.Configuration[1] at runtime
that uses different
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Eric.
> Why not use OSGi? Or is that what you mean by a "container"?
I assume that the quote I gave uses "container" to mean systems like
OSGi (it's from Alan, maybe he will correct me if I'm wrong). So yes,
I mean that.
I am trying to find a w
Why not use OSGi? Or is that what you mean by a "container"?
Eric.
On Tue, Oct 20, 2015 at 6:30 AM, Nicolai Parlog wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi!
>
> There have been a number of threads regarding loading multiple
> versions of the same module. The requiremen
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
