[jira] [Created] (GROOVY-8575) Cannot build project with 2.6.0-alpha-3 dependency using Gradle

["Devin Rosenbauer (JIRA)" <ji...@apache.org>]

Devin Rosenbauer created GROOVY-8575:
----------------------------------------

             Summary: Cannot build project with 2.6.0-alpha-3 dependency using Gradle
                 Key: GROOVY-8575
                 URL: https://issues.apache.org/jira/browse/GROOVY-8575
             Project: Groovy
          Issue Type: Bug
          Components: groovy-jdk
    Affects Versions: 2.6.0-alpha-3
            Reporter: Devin Rosenbauer


Declaring the following dependency in a Gradle build script:
{quote}compile group: 'org.codehaus.groovy', name: 'groovy-all', version: '2.6.0-alpha-3' 
{quote}
Results in the following Gradle error:
{quote}FAILURE: Build failed with an exception.

What went wrong:
 Could not resolve all files for configuration ':Framework:compileClasspath'.
 > Could not find groovy-all.jar (org.codehaus.groovy:groovy-all:2.6.0-alpha-3).
   Searched in the following locations:
 [https://jcenter.bintray.com/org/codehaus/groovy/groovy-all/2.6.0-alpha-3/groovy-all-2.6.0-alpha-3.jar]
{quote}
That file, of course, is missing, and I do not expect it to be there. Gradle should be able to derive dependencies from the .pom file, which is present.

With debug on, I see Gradle appropriately evaluating the dependencies from the POM, then:
{quote}{{15:51:05.979 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.ivyresolve.CachingModuleComponentRepository] Detected non-existence of artifact 'groovy-all.jar (org.codehaus.groovy:groovy-all:2.6.0-alpha-3)' in resolver cache}}
{quote}
This works with all other version strings. One additional oddity: '2.6.0-alpha-2' actually _has_ a groovy-all.jar in Maven Central, whereas 2.5* groovy-all downloads all of the dependency JARs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)