-
Bug
-
Resolution: Not an Issue
-
P1
-
9
-
java version "9-internal"
Java(TM) SE Runtime Environment (fastdebug build 9-internal+0-2016-09-21-113038.cbensen.jdk9udev)
Java HotSpot(TM) 64-Bit Server VM (fastdebug build 9-internal+0-2016-09-21-113038.cbensen.jdk9udev, mixed mode)
Please find the attachment readmod.zip which contains readmod module.
ISSUE:
if both "MainJar" and "ClassPath" are mentioned via RelativeFileSet BaseDirectory then mainJar should be picked from RelativeFileSet mentioned BaseDirectory instead currently jars are picked from relative to current working directory because of which you cannot execute JAVA_API from other than jars directory.
i mean you have to be in jars directory to execute Javapackager.
EXECUTION LOG:
Please find the attachment maclog for execution log.
EXPECTED RESULTS:
Javapackager API should be able to execute from any directory in the system not only from directory containing jars.
ISSUE:
if both "MainJar" and "ClassPath" are mentioned via RelativeFileSet BaseDirectory then mainJar should be picked from RelativeFileSet mentioned BaseDirectory instead currently jars are picked from relative to current working directory because of which you cannot execute JAVA_API from other than jars directory.
i mean you have to be in jars directory to execute Javapackager.
EXECUTION LOG:
Please find the attachment maclog for execution log.
EXPECTED RESULTS:
Javapackager API should be able to execute from any directory in the system not only from directory containing jars.
