[GRADLE-2978] Groovy 'indy' version is not reported when the 'dependencies' help task is run. Created: 18/Dec/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 0


When running the 'dependencies' help task, the 'indy' (invoke dynamic) portion of the Groovy version is left out of the task output. I am assuming that any classifiers are omitted from the report. I'm not sure if this is considered a bug, but I did find it confusing since we had an issue where both indy and non-indy versions were being pulled in via transitive dependencies (which was causing problems for us!). I've included an example - using the build file below, run the following command:

gradle dependencies --configuration compile

Task Output:

compile - Compile classpath for source set 'main'.
--- org.codehaus.groovy:groovy-all:2.2.1

I've created the copyDeps task to demonstrate that the indy version of Groovy is actually being downloaded and used by the build.

Build file:

apply plugin: 'groovy'

ext {
groovyVersion = '2.2.1'

repositories {

dependencies {
compile "org.codehaus.groovy:groovy-all:${groovyVersion}:indy"

task copyDeps(type: Copy, dependsOn: build) {
from configurations.compile
into 'build/deps'

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:36:35 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.