[
https://issues.apache.org/jira/browse/GROOVY-8751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578972#comment-16578972
]
Paul King commented on GROOVY-8751:
-----------------------------------
Yes, we really liked the all jar too. Unfortunately, it isn't really compatible
with the new world of modules in JDK9+. See the release notes for more details.
You can create your own uber jar with jarjar or similar but you have to make
sure that you never get that jar and a non-all groovy jar in your module path
on JDK9+, otherwise you'll face the split package restriction. We could have
provided such a jar ourselves but if we made it available in a repo somewhere
you can be sure that it would end up directly or transitively on someones
classpath or modulepath.
If you are behind a firewall and have strict control of your build process you
might have more luck controlling that.
> Why is the groovy-all.jar no longer included in the SDK zip file in 2.5.1 ?
> ---------------------------------------------------------------------------
>
> Key: GROOVY-8751
> URL: https://issues.apache.org/jira/browse/GROOVY-8751
> Project: Groovy
> Issue Type: Question
> Components: groovy-jdk
> Affects Versions: 2.5.1
> Reporter: David Goblirsch
> Priority: Minor
>
> In previous versions the SDK zip bundle included a directory named
> "embeddable" which included two jars, "groovy-all-2.4.15.jar" and
> "groovy-all-2.4.15-indy.jar", for example.
> Starting with version 2.5.1, I no longer see this directory or these jars in
> the distribution. This is an inconvenience for those of us behind corporate
> firewalls. Having a complete distribution in one download was simpler.
> Why is the "embeddable" directory and these two jars no longer provided?
> Thank you.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
