JDK-8227058 : Regressions related to no longer setting user.dir
  • Type: Bug
  • Component: tools
  • Sub-Component: jpackage
  • Affected Version: internal
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-07-02
  • Updated: 2019-07-05
  • Resolved: 2019-07-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
internalFixed
Related Reports
Relates :  
JDK-8226904 - current working directory wrong running jpackage app
Description
JDK-8226904 changed the applauncher to no longer set the current directory before launching java.
The launch of java depended on several entries in the cfg file (main-jar, app.runtime, app.classpath, and --module-path).
Each of these previously depended on the current directory being set to the app dir.

app.runtime has always been $APPDIR/runtime.

Now the --module path, the main-jar, and each entry in the classpath must also be based on $APPDIR
Comments
webrev: http://cr.openjdk.java.net/~herrick/8227058/
03-07-2019