[GRADLE-2773] Deprecation warning emitted when using a user-added configuration named "groovy" Created: 09/May/13  Updated: 24/Jan/17  Resolved: 24/Jan/17

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

Type: Bug
Reporter: Luke Daley Assignee: Unassigned
Resolution: Fixed Votes: 0


Gradle 1.5 deprecated the special "groovy" configuration in favour of inferring the groovy dependency from the classpath.

The deprecation warning is a little overzealous in that it warns if the user creates their own configuration named 'groovy'.

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 [ 24/Jan/17 ]

I don't see anymore deprecation warning with 3.3. Based on the following build script:

apply plugin: 'groovy'

configurations {

repositories {

dependencies {
    groovy 'org.codehaus.groovy:groovy-all:2.4.7'
    compile 'org.codehaus.groovy:groovy-all:2.4.7'
Generated at Wed Jun 30 12:31:07 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.