8207690: Parsing API for classpath and similar path strings

[Weijun Wang]

https://docs.oracle.com/javase/8/docs/technotes/tools/windows/classpath.html#A1100762

This is not about the wildcard parsed by the shell. The bug synopsis mentions "classpath" and I am just curious if it covers this feature. I don't have my own user case for it.

--Max

> On Sep 11, 2018, at 10:48 PM, Roger Riggs <roger.riggs at oracle.com> wrote:
> 
> Hi,
> 
> What would the use case be for that?
> 
> A search path is usually just a sequence of file paths;  wildcard expansion is not includes.
> Wildcards are significant only in shell contexts, though the expansion is done by the shell on Unix and by the application on Windows;  it would add a fair bit of complexity.
> 
> Roger
> 
> 
> On 9/11/18 10:44 AM, Weijun Wang wrote:
>> Is the wildcard character allowed in the input?
>> 
>> I'm thinking of the wildcard support in classpath.
>> 
>> --Max
>> 
>>> On Sep 11, 2018, at 2:16 AM, Roger Riggs <Roger.Riggs at oracle.com> wrote:
>>> 
>>> Please review the API and implementation of an API to parse Path strings.
>>> Two methods are added to java.nio.file.Paths to parse a string using the path separator delimiter
>>> and return either List<String> or List<Path>.  Empty path elements are ignored.
>>> 
>>> For compatibility with current URLClassPath behavior the internal implementation handles
>>> replacement of empty paths.
>>> 
>>> Webrev:
>>> http://cr.openjdk.java.net/~rriggs/webrev-8207690_parsing_api_for_classpath_and_similar_path_strings/
>>> 
>>> CSR:
>>>   https://bugs.openjdk.java.net/browse/JDK-8208208
>>> 
>>> Thanks, Roger
>>> 
>