> On 8 Dec 2016, at 09:34, Volker Simonis <volker.simo...@gmail.com> wrote: > > Hi Vincent, > > the bug is closed and can't be looked at outside Oracle. > Can you please make it visible for everybody.
Sorry. I’ve just corrected that. > > Also, this is a change of the public API so it requires a CCC > request/approval. I’ve a CCC prepared which I will submit if there is consensus on the proposed API. > > Finally, this seems to be clearly a feature and not a bug so it > requires an FC extension request [1] Right. I’ve begun that too. > > Thanks, > Volker > > [1] http://openjdk.java.net/projects/jdk9/fc-extension-process > > On Wed, Dec 7, 2016 at 5:32 PM, Vincent Ryan <vincent.x.r...@oracle.com> > wrote: >> A hexdump facility has been available for many, many years via an >> unsupported class: sun.misc.HexDumpEncoder. >> Although that class was always unsupported, it was still accessible. That >> accessibility changes with Jigsaw so I’m proposing >> a very simple replacement in a new and supported class: java.util.HexDump. >> >> Thanks. >> >> Bug: https://bugs.openjdk.java.net/browse/JDK-8170769 >> Webrev: http://cr.openjdk.java.net/~vinnie/8170769/webrev.00/ >>
