[Bug 66432] New: Launcher does not catch all forms of classpath definition using "--noclasspath"

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=66432

            Bug ID: 66432
           Summary: Launcher does not catch all forms of classpath
                    definition using "--noclasspath"
           Product: Ant
           Version: 1.10.13
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core
          Assignee: notifications@ant.apache.org
          Reporter: jgsuess@gmail.com
  Target Milestone: ---

The Launcher org.apache.tools.ant.launch.Launcher has an option
"--noclasspath", whose purpose it is to suppress the collection of a Java
classpath defined using "-cp".

However, the Java 11 release and following standard options includes
alternative forms of "-cp":

--class-path classpath, -classpath classpath, or -cp classpath
A semicolon (;) separated list of directories, JAR archives, and ZIP archives
to search for class files. Ref below

https://docs.oracle.com/en/java/javase/11/tools/java.html#GUID-3B1CE181-CD30-4178-9602-230B800D4FAE__GUID-8CAE5D46-28F3-49B8-AAF5-EE79DC092E5D

This means that the launcher fails to suppress these forms of classpath
definition.

It seems that this is an error or omission.

Either the function is partial, and to be removed, or incomplete and should be
extended to cover.

There is also very terse documentation on the launcher, so the intent is hard
to judge.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 66432] Launcher does not catch all forms of classpath definition using "--noclasspath"

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=66432

Jörn Guy Süß <jg...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #1 from Jörn Guy Süß <jg...@gmail.com> ---
Based on a misunderstanding of functionality due to limited documentation on
the launcher class. Needed to read code of the dispatch script to understand
responsibility of the launcher.

-- 
You are receiving this mail because:
You are the assignee for the bug.