Gradle Deprecations

Gradle Deprecations – Common Mistakes

Maven Repository

OLD

mavenCentral()

NEW

repositories {
  maven {
    url “http://repo1.maven.org/maven2/”
  }
}


Intellij Idea Plugin

OLD

apply plugin:’idea’

NEW

Do not use, IntelliJ will import Maven, Gradle and Eclipse projects (unless you are using a dinosaur version of Idea).

The plugin generates a very very old IntelliJ IDEA project, which is exactly
the same out-of-date plugin provided by Maven (hmm… curious?).


Dependencies

OLD

groovy localGroovy()

or

groovy “org.codehaus.groovy:…”

NEW

compile “org.codehaus.groovy:groovy-all:2.1.6″


Example

        apply plugin:'groovy'
        apply plugin:'eclipse'

        repositories {
          maven {
            url "http://repo1.maven.org/maven2/"
          }

        task wrapper(type:Wrapper) { gradleVersion = '1.6' }

        dependencies {
          compile "org.codehaus.groovy:groovy-all:2.1.6"
          testCompile "org.spockframework:spock-core:0.7-groovy-2.0"
        }
    

About Gordon

Technology enthusiast primarily focused on Java and Open Source projects. Spring Certified Professional and Trainer. http://twitter.com/gdickens http://linkedin.com/in/gordondickens http://github.com/gordonad
This entry was posted in Eclipse, Gradle, Groovy, Maven and tagged , , , , , . Bookmark the permalink.

3 Responses to Gradle Deprecations

  1. joschi says:

    The Gradle User Guide for the current release candidate (1.7-rc-1) still recommends using mavenCentral(). Where did you find the information that this syntax is being deprecated?

    Also the IntelliJ IDEA plugin is still very useful because JetGradle (the plugin for IntelliJ IDEA which handles Gradle build files) still has some problems with changing dependencies. Also the Gradle IDEA plugin allows customizing the IDEA projects/modules very easily which obviously wouldn’t work when importing the Gradle build file directly.

  2. Matt Veitas says:

    Where did you read that the mavenCentral() was deprecated?

  3. Gordon says:

    Now for the life of me, I can not repeat it. Still looking into it, running into proxy issues with Gradle (all Groovy projects), a simple clear, precise example of the file location would do wonders for everyone. The documentation is cursory at best and the O’Reilly is almost the same as the site docs.

Leave a Reply

Your email address will not be published. Required fields are marked *


*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>