8207690: Parsing API for classpath and similar path strings
roger.riggs at oracle.com
Tue Sep 11 15:05:23 UTC 2018
Right, that is a description of the shell environment on Windows and how
the java launcher behaves.
On Windows the launcher expands wildcards when evaluating classpath from
and the command line args. After they are expanded the java.class.path
property is set.
The proposed API can be used with other paths and does not expand wildcards.
On 9/11/18 10:53 AM, Weijun Wang wrote:
> 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.
>> On Sep 11, 2018, at 10:48 PM, Roger Riggs <roger.riggs at oracle.com> wrote:
>> 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.
>> 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.
>>>> 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.
>>>> Thanks, Roger
More information about the core-libs-dev