[
https://issues.apache.org/jira/browse/DERBY-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16697394#comment-16697394
]
Rick Hillegas commented on DERBY-7016:
--------------------------------------
Here's what the experts have to say. Alan Bateman posted the following response
to the Open JDK core-libs-dev mailing list on an email thread titled "-jar
option and the modulepath":
"There is no support for executable modular JARs at this time. It's part of a
bigger topic that is tracked as #MultiModuleExecutableJARs. Some prototypes
during JDK 9 but the decision at the time was to defer it to some future
effort. So when you run with `java -jar` then it puts the JAR file on the class
path (exactly as it did in all previous releases)."
> Adjust the set*CP scripts to include derbyshared.jar and to set a MODULEPATH
> variable as well
> ---------------------------------------------------------------------------------------------
>
> Key: DERBY-7016
> URL: https://issues.apache.org/jira/browse/DERBY-7016
> Project: Derby
> Issue Type: Bug
> Components: Demos/Scripts
> Affects Versions: 10.15.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Priority: Major
> Fix For: 10.15.0.0
>
> Attachments: derby-7016-01-aa-addSharedModule-setModulepath.diff,
> derby-7016-01-ab-addSharedModule-setModulepath.diff
>
>
> The classpath-setting scripts need to include derbyshared.jar in the
> classpath and set MODULEPATH as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
