Use Gradle's provided Groovy library as default for 'groovy' dependency (Groovy plugin)

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Resolution: Won't Fix
  • Affects Version/s: 1.0-milestone-1
  • Fix Version/s: 1.0

Description

The Groovy plugin requires the definition of the 'groovy' dependency like this:

apply plugin: 'groovy'

dependencies {
    groovy group: 'org.codehaus.groovy', name: 'groovy', version: '1.7.6'
}

Gradle already ships with a groovy-all library. I think it would be great if we could simply assign that library so the user doesn't have to define the dependency. If the user wants to assign a different Groovy version he/she can still do that in the dependencies closure. At the moment I am using this workaround:

dependencies {
    groovy fileTree(dir: new File(gradle.gradleHomeDir, 'lib'), includes: ['**/groovy-all-*.jar'])
}

Activity

Hide
Permalink
Luke Daley added a comment -

Using it as a default is a bit risky, but there is a shorthand notation for this which is a good compromise.

groovy localGroovy()

This was added to the docs in 1.0 m4.

Note that this doesn't export as a dependency, so won't show up in your POM if you are producing one (which is usually the desired behaviour if you want to use Gradle's groovy).

Show
Luke Daley added a comment - Using it as a default is a bit risky, but there is a shorthand notation for this which is a good compromise. 
groovy localGroovy()
This was added to the docs in 1.0 m4. Note that this doesn't export as a dependency, so won't show up in your POM if you are producing one (which is usually the desired behaviour if you want to use Gradle's groovy).

People

  • Assignee:
    Luke Daley
    Reporter:
    Benjamin Muschko
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: