Since your ToolProvider-based program doesn't explicitly require
jdk.incubator.jpackage, it won't be in the module graph. It should work
fine if you run with:
$ java --add-modules jdk.incubator.jpackage ...
-- Kevin
On 2/24/2020 8:23 AM, Michael Hall wrote:
On Feb 22, 2020, at 7:02 PM, Michael Hall <mik3h...@gmail.com
<mailto:mik3h...@gmail.com>> wrote:
Currently, at least for Runtime exec including the commands with the
application does no good.
Just to check would this be known expected behavior?
Or a known issue?
Or something that should have a bug report filed against it?
I additionally looked at using ToolProvider with jpackage as it is
indicated to support that but it does not appear to work either at
this time.
This can be verified independently of my application. I’m not real
familiar but based on a googled example.
import java.util.spi.ToolProvider;
public class ToolProviderTest {
public static void main(String[] args) {
ToolProvider tool = ToolProvider.findFirst(args[0])
.orElseThrow(() -> new IllegalStateException("can not find tool " +
args[0]));
System.out.println("tool " + tool);
}
}
(base) Michaels-MBP:~ mjh$ java -cp . ToolProviderTest jlink
tool jdk.tools.jlink.internal.Main$JlinkToolProvider@1f32e575
(base) Michaels-MBP:~ mjh$ java -cp . ToolProviderTest jar
tool sun.tools.jar.JarToolProvider@2a84aee7
(base) Michaels-MBP:~ mjh$ java -cp . ToolProviderTest jpackage
Exception in thread "main" java.lang.IllegalStateException: can not
find tool jpackage
at ToolProviderTest.lambda$main$0(ToolProviderTest.java:8)
at java.base/java.util.Optional.orElseThrow(Optional.java:401)
at ToolProviderTest.main(ToolProviderTest.java:8)
(base) Michaels-MBP:~ mjh$ java --list-modules | grep jpackage
jdk.incubator.jpackage@14
Probably due to jpackage incubator status? But for now programmatic
testing of jpackage does not seem possible.
