-
Bug
-
Resolution: Fixed
-
P3
-
8u91, 9
-
b124
-
x86_64
-
windows_7
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8168217 | 8u152 | Dmitry Markov | P3 | Resolved | Fixed | b01 |
JDK-8163609 | 8u121 | Dmitry Markov | P3 | Resolved | Fixed | b01 |
JDK-8158179 | 8u112 | Dmitry Markov | P3 | Resolved | Fixed | b01 |
JDK-8159647 | 8u111 | Dmitry Markov | P3 | Resolved | Fixed | b01 |
JDK-8158835 | 8u102 | Dmitry Markov | P3 | Resolved | Fixed | b11 |
JDK-8158395 | 8u92 | Dmitry Markov | P3 | Resolved | Fixed | b32 |
JDK-8167703 | emb-8u121 | Dmitry Markov | P3 | Resolved | Fixed | b01 |
JDK-8162035 | emb-8u111 | Dmitry Markov | P3 | Resolved | Fixed | b01 |
JDK-8158180 | 7u121 | Dmitry Markov | P3 | Resolved | Fixed | b01 |
JDK-8158832 | 7u111 | Dmitry Markov | P3 | Resolved | Fixed | b11 |
JDK-8158284 | 6u131 | Dmitry Markov | P3 | Closed | Won't Fix |
java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Windows 7 Pro, 64 bit
A DESCRIPTION OF THE PROBLEM :
When using javaws update 91, the application working directory is now an equivalent of {java.home}, rather than the current (command invocation) directory.
As a result, an application invoked as:
$ cd C:\Users\mbrunecky
$ javaws -open Foo.properties <jnlp_url>
trying to open "Foo.properties" attempts to open {java.home}/Foo.properties
instead of "C:\Users\mbrunecky\Foo.properties".
(and obviously fails).
In addition, any files created by such application are created in {java.home}
rather than the current working directory (unless file specification includes an explicit path).
This is another, but more serious consequence than the (related) bug
(I want to make sure bug 8154899 is 'fixed RIGHT")
REGRESSION. Last worked in version 8u77
ADDITIONAL REGRESSION INFORMATION:
java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Within JNLP application, assuming arguments -open Foo.properties, add line
System.err.println("Arg " + args[0] " + new File(args[1]).getAbsolutePath());
Once invoked using:
javaws -open Foo.properties <jnlp_url>
you will see that instead of resolving Foo.properties to the current working directory, the "Foo.properties" will resolve to {java.home}/Foo.properties
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
javaws -open Foo.properties <jnlp_url>
resolving to
{command working directory}/Foo.properties
ACTUAL -
javaws -open Foo.properties <jnlp_url>
{java.home}/Foo.properties
(file not found)
ERROR MESSAGES/STACK TRACES THAT OCCUR :
None, -open option has become useless
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Revert to java 1.8.0_77
- backported by
-
JDK-8158179 Application started using javaws now starts in {java.home} rather than current directory
-
- Resolved
-
-
JDK-8158180 Application started using javaws now starts in {java.home} rather than current directory
-
- Resolved
-
-
JDK-8158395 Application started using javaws now starts in {java.home} rather than current directory
-
- Resolved
-
-
JDK-8158832 Application started using javaws now starts in {java.home} rather than current directory
-
- Resolved
-
-
JDK-8158835 Application started using javaws now starts in {java.home} rather than current directory
-
- Resolved
-
-
JDK-8159647 Application started using javaws now starts in {java.home} rather than current directory
-
- Resolved
-
-
JDK-8162035 Application started using javaws now starts in {java.home} rather than current directory
-
- Resolved
-
-
JDK-8163609 Application started using javaws now starts in {java.home} rather than current directory
-
- Resolved
-
-
JDK-8167703 Application started using javaws now starts in {java.home} rather than current directory
-
- Resolved
-
-
JDK-8168217 Application started using javaws now starts in {java.home} rather than current directory
-
- Resolved
-
-
JDK-8158284 Application started using javaws now starts in {java.home} rather than current directory
-
- Closed
-
- relates to
-
JDK-8154899 System property 'user.dir' now set to 'java.home' value rather than user's working directory
-
- Closed
-