Can't speak for Per, but for us, it would be patently absurd to embed all the
libraries into our executable. It's partially the storage, for we have a number
of applications which share the libs, but much more important would be the
upload time when we changed our code (which happens pretty ofte
Per,
Out of curiosity why wouldn’t you want to include groovy jars in every jar
bundle. Is it the maintenance of groovy security patches? It isn’t the
storage is it?
From: o...@ocs.cz
Sent: Sunday, February 23, 2025 11:27 AM
To: users@groovy.apache.org
Subject: Re: Groovy -jar
Per
Per,
we sort of have debated this some time ago, when groovy-all.jar was, sadly,
removed.
We use a similar approach, nevertheless, we need much more complex classpath.
On the other hand, since we deploy WebObjects, we just could take the standard
NeXT/Apple WO launch script and very slightly c
Thanks for this!
For the use case you mention it makes perfect sense to do it that way.
Since I don't want to include groovy jars in every jar bundle, I ended
up with this instead:
https://github.com/Alipsa/groovyjar/blob/main/groovyjar
I still think something similar would be nice and usefu
