RFR 8194746: (fs) Add equivalents of Paths.get to Path interface

Alan Bateman Alan.Bateman at oracle.com
Thu Mar 8 08:07:08 UTC 2018


On 08/03/2018 00:37, Paul Sandoz wrote:
>
>> On Mar 7, 2018, at 1:57 PM, Brian Burkhalter <brian.burkhalter at oracle.com> wrote:
>>
>> https://bugs.openjdk.java.net/browse/JDK-8194746
>> http://cr.openjdk.java.net/~bpb/8194746/webrev.00/
>>
> Path.java
>
>   639      * {@link Paths#get(URI) Path.get}{@code (}<i>p</i>{@code .toUri()).equals(}<i>p</i>
>
> The link refers to Paths not Path.
>
> Nice cleanup. It was always a painful for those new to this area to find the Path factories.
>
We also to add @since 11 to the new methods and I'm wondering about 
adding an @apiNote to Path's class description to indicate that it's 
obsolete and that the static methods defined by Path should be used in 
preference. I don't think Paths needs to be deprecated of course, I'm 
just thinking of developers wondering what the Paths class is for.

-Alan


More information about the nio-dev mailing list