[ https://issues.apache.org/jira/browse/GROOVY-9002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17338145#comment-17338145 ]
Paul King commented on GROOVY-9002: ----------------------------------- Adjusted priority from critical => major since there is the obvious workaround of just listing all the required jars. > groovy-all-2.5.4-indy not available in mavenCentral > --------------------------------------------------- > > Key: GROOVY-9002 > URL: https://issues.apache.org/jira/browse/GROOVY-9002 > Project: Groovy > Issue Type: Bug > Components: groovy-runtime > Affects Versions: 2.5.4 > Environment: Groovy / Gradle 5 > Reporter: will mason > Priority: Major > Labels: groovy-all, indy, invokedynamic > > Our Gradle build automatically looks for the Groovy version that matches the > installed Gradel version. This is done because sometimes having an > incompatible Groovy version with the build causes exceptions in the build. > Therefore it is impretive for the matching Groovy artefact be available in > the central repositories. > {noformat} > FAILURE: Build failed with an exception. > * What went wrong: > Could not resolve all files for configuration > ':TestingSupport:compileClasspath'. > > Could not find groovy-all-indy.jar (org.codehaus.groovy:groovy-all:2.5.4). > {noformat} > I've looked in both {{mavenCentral}} and {{jcenter}} and the {{groovy-all}} > indy file is not present. > The [Invoke dynamic support|http://groovy-lang.org/indy.html] documentation > page reports that there are two versions of the Groovy all .JAR used. > The absence of this JAR breaks our build. > If Groovy is no longer supporting the {{-indy}} version of the JAR-s this > should be noted in the documentation. I could find nothing about Invoke > Dynamic in the [Groovy 2.5 release > notes|http://groovy-lang.org/releasenotes/groovy-2.5.html#releasenotes]. -- This message was sent by Atlassian Jira (v8.3.4#803005)