On 16/06/16 12:46, Alan Bateman wrote:
>
> On 16/06/2016 10:11, Andrew Dinn wrote:
>> :
>> Ok, so now the bonus question:
>>
>> Does that mean that it is not possible to implement a Java JVMTI agent
>> as Jigsaw modularised code?
>>
>> I'll add the following to render the question more specific: C
On 16/06/2016 10:11, Andrew Dinn wrote:
:
Ok, so now the bonus question:
Does that mean that it is not possible to implement a Java JVMTI agent
as Jigsaw modularised code?
I'll add the following to render the question more specific: Clearly,
you can deploy an agent that links to related code d
On 15/06/16 17:12, Rémi Forax wrote:
> It is considered as a classical jar not a modular one. It's important
> because it enable backward compatibility without having to provide
> two jars.
Ok, so now the bonus question:
Does that mean that it is not possible to implement a Java JVMTI agent
as Ji
2016/6/15 8:48:57 -0700, [email protected]:
> If a JAR, properly built as a module, is dropped onto the classpath at
> runtime, does it function as a module or does it get treated as part of the
> unnamed module with all types exported?
The latter.
- Mark
It is considered as a classical jar not a modular one. It's important because
it enable backward compatibility without having to provide two jars.
cheers,
Rémi
Le 15 juin 2016 17:48:57 CEST, Paul Benedict a écrit :
>If a JAR, properly built as a module, is dropped onto the classpath at
>runtim
