Hello,
I strongly recommend this test *not* write to java.home in any way,
including undoing the changes afterward.
If that is not possible, I think the test should be updated as suggested
and also turned into a manual test.
Cheers,
-Joe
On 2/23/2017 4:00 PM, Mark Sheppard wrote:
Hi,
Looks OK Mark.
Best
Lance
> On Feb 23, 2017, at 7:00 PM, Mark Sheppard wrote:
>
> Hi,
> please oblige and review the following change
> http://cr.openjdk.java.net/~msheppar/8175177/webrev/
>
> for the issue reported in
> https://bugs.openjdk.java.net/browse/JDK-8175177
>
> the test now expli
You should send this topic to serviceability-dev which is the mailing list for
JMX and other serviceability related issues.
Mandy
> On Feb 23, 2017, at 4:17 PM, Dave Brosius wrote:
>
> Greetings. the method
>
> public static ObjectName getInstance(String domain,
> Hashtable table)
>th
Greetings. the method
public static ObjectName getInstance(String domain,
Hashtable table)
throws MalformedObjectNameException {
return new ObjectName(domain, table);
}
in javax.management.ObjectName allows for a provided Hashtable to
specify properties for the objectname.
Hi,
please oblige and review the following change
http://cr.openjdk.java.net/~msheppar/8175177/webrev/
for the issue reported in
https://bugs.openjdk.java.net/browse/JDK-8175177
the test now explicitly removes the orb.properties file created by the test.
regards
Mark
Thanks Andrew - I recall reading that, but wasn't sure if that was still
the final thinking. Unfortunately, I'm seeing this annotation slip into
codebases (with the corresponding -XX:-RestrictContended), and jigsaw is
surfacing these instances. Looks like we have to wait for panama/valhalla
then
On 23/02/17 17:26, Vitaly Davidovich wrote:
> My understanding was it's in sun.misc as an experimental/"unstable"
> annotation, but that it was incubating there before being made supported
> (and moved out of that package) as it's a legitimately useful feature (the
> manual padding one does today w
Hi all,
I'm curious if anyone knows the future plans for this annotation,
specifically if it's slated to become officially supported in Java SE and
if so, what the timeline looks like (if that exists).
My understanding was it's in sun.misc as an experimental/"unstable"
annotation, but that it was
Here is the webrev for jdk9 :
http://cr.openjdk.java.net/~mbaesken/webrevs/8175000/
? And btw I really wonder - is jexec still needed in future jdk's like jdk10
? Seems it is not used much .
?
In case jexec will stay in the jdk I might add a test for the tool as well,
if there is int
