groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul King (JIRA)" <>
Subject [jira] [Resolved] (GROOVY-8512) 2.6.0-alpha-3
Date Thu, 15 Mar 2018 12:10:00 GMT


Paul King resolved GROOVY-8512.
    Resolution: Not A Problem

This is intentional behavior for 2.5+. To pave the way for Java 9 integration we currently
don't support the all jar anymore - instead the all pom points to the jars that we used to
merge into the all jar. In theory, inclusion of the dependent jars should happen automatically.

In practice, some build tools/plugins/other dependencies might reference the 2.4 all jar directly.
Some appropriate excludes of the old groovy artifact has been reported as fixing that problem
for a number of such cases by other users. Let us know how you go.

> 2.6.0-alpha-3
> -------------
>                 Key: GROOVY-8512
>                 URL:
>             Project: Groovy
>          Issue Type: Bug
>            Reporter: Patrick McCarthy
>            Priority: Major
> I started to observe groovy-all dependency is not resolving for one of my builds from
JCenter with 2.+ version
> Looking directly at the link, the jar file is missing
> {code:java}
> Could not resolve all dependencies for configuration ':compile'.
> 13-Mar-2018 05:25:23	> Could not find groovy-all.jar (org.codehaus.groovy:groovy-all:2.6.0-alpha-3).
> 13-Mar-2018 05:25:23	  Searched in the following locations:
> 13-Mar-2018 05:25:23{code}

This message was sent by Atlassian JIRA

View raw message