# HG changeset patch
# User jbachorik
# Date 1444290031 -7200
# Node ID 8db7e6cffaf4d024e64dc2c25056ccb913c85b67
# Parent  c9211ad104b5e6b966f0d8bd0d819a4d6ceb55bf
8138579: Custom launcher fails to start because of permission problem
Reviewed-by: sspitsyn, dsamersoff

diff -r c9211ad104b5 -r 8db7e6cffaf4 jdk/test/sun/management/jmxremote/bootstrap/CustomLauncherTest.java
--- a/jdk/test/sun/management/jmxremote/bootstrap/CustomLauncherTest.java	Fri Oct 02 18:49:54 2015 +0200
+++ b/jdk/test/sun/management/jmxremote/bootstrap/CustomLauncherTest.java	Thu Oct 08 09:40:31 2015 +0200
@@ -255,8 +255,7 @@
         // and set the executable flag
         Path localLauncherPath = FS.getPath(WORK_DIR, "launcher");
         Files.copy(launcherPath, localLauncherPath,
-                   StandardCopyOption.REPLACE_EXISTING,
-                   StandardCopyOption.COPY_ATTRIBUTES);
+                   StandardCopyOption.REPLACE_EXISTING);
         if (!Files.isExecutable(localLauncherPath)) {
             Set<PosixFilePermission> perms = new HashSet<>(
                 Files.getPosixFilePermissions(