Hi guys, We still have a few issues with java 11:
1. we run with warnings - mainly cause of java.base reflection we do like in Unsafe 2. we don't support modules, 3. owb itself is not module friendly - and please don't add automatic module name, it would break the reflection we do moving warnings to exceptions. I think it can be worth investigating module-info addition - shouldn't hurt in java 8 and can be generated with a maven plugin - asm based - so no need to move to toolchain if it is not that nice on dev side. We can also need to start playing with Module API which is a bit more impacting and can really require toolchain or to have our own asm generator or at least some advanced reflection. Personnally with GraalVM noise and the reject of JPMS I think modules will not make their path to users with warning which can be error depending how the JVM is tuned so can be good to solve that. Another option I thought about was to have a dedicated classloader to host the proxies and not use defineClass in classloaders we don't own at all, this is a good option but from memory it can have some limitations with visibility of classes, can be tricky to have the right tccl - not sure it would affect it much - and maybe some perf issues? Any known opinion or trick to make us better? Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance>
