@jeoj @CedricChampeau @jeoj I just tried our build with the downgraded classpath lib and got further, but not through: https://t.co/T5Xo4Shh4C Checked the jakarta interceptor api jar and this time it has no module information at all. Isn't the jar name supposed to build the module name in these cases?
@pbakker just tried out the awesome gradle-modules-plugin and it works really nicely - except with modularity.mixedJavaRelease set in a multi module build.
@jeoj @CedricChampeau@pbakker From what I can see in https://t.co/9WLaGIJDiA is that they changed to an antrun jar update to include the mdoule-info. That seems to have broken it then
@vlad_mihalcea@bsideup@myfear In that case... thank you for your OSS support. Just recently wanted to use Hibernate Types for jsonb columns and it all worked very well... till I noticed we also have to support H2 for unit tests. Well, let me say, the final decision on that is not through yet.
Groovy was announced 15 years ago today by @jstrachan (first commits to public repo was 15 years yesterday). Over 160 releases, 320+ contributors and 100+million downloads later and it's still going strong. Happy birthday #groovylang!
@mojavelinux@asciidoctor@mgreau So there is no load path based solution known right now. Thanks, but that my mean I cannot use asciidoctor in my case. Too bad!
@ApacheGroovy@PaoloDiTommaso not really, that was in infant stages of Graal. I think Groovy on Graal would require a very different approach than for Ruby
@leventov@CedricChampeau@paulk_asert Using internal mechanisms is never desired by the implementers of that mechanism. So not illegal per se, but it can stop working any time
@CedricChampeau@leventov@paulk_asert We are creating GroovyMagic. It lasts, because it is a magic accessor implementation. One of the old magic secrets in Java.