Again thanks, but this seems sort of at the dangerous side. Correct me please
if I am wrong, but I understand JVM loads the classes on-demand when they are
needed, not all at the launch time.
That would mean that a well- but not completely-tested application (and we all
know it is just not
Well thanks, but I do not even know what Maven or Gradle is. I presume those
probably would be build systems, which both could generate the proper
groovy-all JAR, right? Systems presumably well-known and used daily by all
those who maintain and improve Groovy itself (kudos to you all!), but of
I can only comment on our experience:
- For most of our projects simply replacing groovy-all with the core groovy
module has worked fine as most of our projects don't (didn't) make use of the
classes that are not present in the core groovy module.
- For the projects that did need missing
Hi there,
> On 16 May 2020, at 14:17, OCsite wrote:
> First, can you (or anyone) please suggest what to do with my classpath now
> when groovy-all's gone?
I still can't see a reasonable solution for that :( All the documentation I've
found so far is
>
