groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Sun (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GROOVY-9002) groovy-all-2.5.4-indy.jar not available in mavenCentral or jcenter
Date Wed, 20 Feb 2019 04:45:00 GMT

    [ https://issues.apache.org/jira/browse/GROOVY-9002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772618#comment-16772618
] 

Daniel Sun commented on GROOVY-9002:
------------------------------------

 _2.5+:_ A "fat pom" {{groovy-all-x.y.z.pom}} referring to the core plus all modules (excluding
optional ones). In order to cater to the module system of Java 9+, the {{groovy-all-x.y.z.jar}} file
is no longer available.

Gradle usage:
{code:java}
org.codehaus.groovy:groovy-all:x.y.z
{code}
Maven usage:
{code:java}
<groupId>org.codehaus.groovy</groupId>
<artifactId>groovy-all</artifactId>
<version>x.y.z</version>
<type>pom</type> <!-- required JUST since Groovy 2.5.0 -->
{code}

> groovy-all-2.5.4-indy.jar not available in mavenCentral or jcenter
> ------------------------------------------------------------------
>
>                 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: Critical
>              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
(v7.6.3#76005)

Mime
View raw message