Hmmm, I don't know if Paul has some comeback, but to me you make a very
convincing point...
In that case the best way forward to me seems to be to
1) Ask non-@CompileStatic Groovy users who can afford the time to switch
to the invoke dynamic variety of the Groovy jars and report back on
perform
No there is not. But it should be pretty easy to do so, using Gradle shadow
plugin for example.
2017-12-18 16:59 GMT+01:00 :
> "The "all" sources is still produced. But there's no all jar anymore."
>
>
>
> Is there a way to get back to being able to produce an all jar? I
> actually leverage the
"The "all" sources is still produced. But there's no all jar anymore."
Is there a way to get back to being able to produce an all jar? I actually
leverage the embeddable jar for embedding in another OSGi bundle. I was
humming along with adding Groovy 2.5 support through beta2 and now it seems
On 18.12.2017 01:01, MG wrote:
Just came across this as an example where using Groovy 2.4.6
invokedynamic seems to have been much slower than the older callsite
caching mechanism:
https://www.linkedin.com/pulse/how-make-groovy-fast-java-david-e-jones
(https://dzone.com/articles/how-to-make-gro
