"InOutPathTest(IMAGE, --app-content same as --input)" test case of InOutPathTest test suite produces an invalid app image on macOS platform.
It runs the following jpackage command line:
---
jpackage --dest output --name InOutPathTest Hello --app-content output/InOutPathTest.app ...
---
The value of the `--app-content` parameter equals the name of the output app image folder. This makes jpackage copy folder "output/InOutPathTest.app" in "output/InOutPathTest.app/Contents" folder invalidating its structure for signing. In some environments this will make codesign tool fail with the error:
---
/usr/bin/codesign -s - -vvvv --force ./test.b682c86a/output/InOutPathTest.app
[20:46:50.886] Output:
./test.b682c86a/output/InOutPathTest.app: code object is not signed at all
---
It runs the following jpackage command line:
---
jpackage --dest output --name InOutPathTest Hello --app-content output/InOutPathTest.app ...
---
The value of the `--app-content` parameter equals the name of the output app image folder. This makes jpackage copy folder "output/InOutPathTest.app" in "output/InOutPathTest.app/Contents" folder invalidating its structure for signing. In some environments this will make codesign tool fail with the error:
---
/usr/bin/codesign -s - -vvvv --force ./test.b682c86a/output/InOutPathTest.app
[20:46:50.886] Output:
./test.b682c86a/output/InOutPathTest.app: code object is not signed at all
---
- relates to
-
JDK-8325089 jpackage utility creates an "infinite", undeleteable directory tree
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk/ac82a8f8
-
Review(master) openjdk/jdk/21909