Daniel, > On 16 May 2020, at 10:58, Daniel.Sun <sun...@apache.org> wrote: > The joint compilation issue should be fixed in Groovy 3.0.4, which will be > released in a couple of days. > > If you want to try in a hurry, here is link to SNAPSHOT: > https://github.com/apache/groovy/actions/runs/106435124
great, thanks; I've suceeded to check quickly and my project is built completely! Great! (Incidentally, seems the compiler now does not understand the --indy switch. I'd sugges — if it does not make any sense anymore —, to still recognise it and just emit a warning that the switch does not do anything anymore. That it prevents compilation is pretty bad for project backward compatibility. Running's not that easy. First, can you (or anyone) please suggest what to do with my classpath now when groovy-all's gone? The only solution I've found to be able to run my application was to add all JARs from groovy/lib to classpath; that's darn inconvenient for testing and would be a proper hell for deployment :( Aside of that it seems it runs more or less all right. Some of my ASTTs seem to be incompatible with the new stuff alas, but that I'll have to pursue in detail before I either simply fix it at my side or ask here for a help :) Thanks again a big lot! OC
