> On Feb 14, 2017, at 4:38 AM, Andrew Haley wrote:
>
> On 14/02/17 14:37, Alan Bateman wrote:
>> --patch-module can be used to patch any module in the boot layer. So if
>> you are looking to override or add classes then --patch-module should work.
>
> Aha! Thanks,
Does it?
I lost track a bit but why are we exporting jdk.vm.ci.services to the world now?
module jdk.internal.vm.ci {
-exports jdk.vm.ci.services to jdk.internal.vm.compiler;
+exports jdk.vm.ci.services;
> On Apr 18, 2017, at 9:16 PM, Doug Simon wrote:
>
> (adding hotspot-compiler-dev)
>
> Ple
e is the restriction that only
jdk.internal.vm.compiler can use jdk.vm.ci.services? After all, this is a
security issue.
>
> Mandy
>
>> On Apr 19, 2017, at 11:24 AM, Christian Thalinger
>> wrote:
>>
>> I lost track a bit but why are we exporting jdk.vm.ci.
> On Apr 19, 2017, at 9:27 AM, Doug Simon wrote:
>
>>
>> On 19 Apr 2017, at 21:04, Mandy Chung wrote:
>>
>>
>>> On Apr 19, 2017, at 11:55 AM, Christian Thalinger
>>> wrote:
>>>
>>>
>>>> On Apr 19, 2017, at 8:3
eMethodAccessorImpl.invoke0(Native
>>> Method)
>>> at
>>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>> at
>>> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invo
> On Apr 27, 2017, at 11:51 AM, Doug Simon wrote:
>
>>
>> On 27 Apr 2017, at 18:44, Christian Thalinger wrote:
>>
>> Thanks for doing this. I have a hard time following what’s happening :-)
>>
>> src/jdk.internal.vm.compiler/
> On Jul 24, 2015, at 10:10 AM, Sergey Bylokhov
> wrote:
>
> After the latest merge I got some issue, I assume related to this fix.
> Can somebody take a look to this code:
>
> import java.net.URI;
> import java.nio.file.*;
> import java.nio.file.attribute.BasicFileAttributes;
>
> public clas
