criptor is evident.
What if patched module descriptors are only effective when a command
line option is present, say "--allow-patch-descriptors", or something
like that?
Thanks!
--
Simone Bordet
---
Finally, no matter how good the architecture and design are,
to deliver bug-free softw
ith a legit module-info.class
java --module-path jetty-client.jar:library.jar:app.jar --module
app/com.app.Main
With this command line, does the Java runtime parse and enable the
patched descriptor contained in library.jar, opening up jetty-client?
If not, how would you enable it in Maven?
Am I missing
return Optional.of(uri);
} else {
return delegate().find(name);
}
where delegate() returns the non-patched part of the module.
So it either returns one, or the other.
While debugging, I set r=null to see what the delegate would find, and
it does find /E:/test-classpath-demo-master/target/clas
s get a MethodHandle on itself.
I tested this with 11, 15, and 16+25, all fail.
I have a simple reproducer, and I can open an OpenJDK bug.
Thanks!
--
Simone Bordet
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability
Hi,
On Tue, Nov 24, 2020 at 7:35 PM Alan Bateman wrote:
> On 24/11/2020 18:21, Simone Bordet wrote:
> > Hi,
> >
> > testing the Jetty MethodHandle usages we encountered this situation:
> >
> > .class org.openjdk.mh.Main
> >
> > Class klass
