On 31/07/2018 06:33, Milen Dyankov wrote:
Thank you for the clarification Alan,
it seams ALL-DEFAULT does not work with jlink but that is OK as I can
easily find those modules while running my assembly tool and pass the list
to jlink.
Right, the ALL-DEFAULT token doesn't mean anything at link ti
Thank you for the clarification Alan,
it seams ALL-DEFAULT does not work with jlink but that is OK as I can
easily find those modules while running my assembly tool and pass the list
to jlink.
The only difference between what I find and what you posted (I assume 7 was
a typo as your list contains
On 30/07/2018 11:41, Milen Dyankov wrote:
:
So am I right to assume that any application server like software is
expected to always run on top of all standard JDK modules that export
"java.*" packages? I mean, say there is an application server that runs on
top of "minimal" JPMS created with jli
Thank you Alan,
that is what I originally thought. It's just your comment in the other
thread made me think there may be a possibility I was not aware of.
So am I right to assume that any application server like software is
expected to always run on top of all standard JDK modules that export
"ja
On 30/07/2018 10:16, Milen Dyankov wrote:
In response to a question posted on this list [1] some time ago, Alan
Bateman stated "You can override *any* module (except java.base) with an
alternative implementation in the child layer". Is that true for the
standard JDK modules? If so, is there any d
