Giter VIP home page Giter VIP logo

Comments (8)

tinyrye avatar tinyrye commented on July 16, 2024 1

I had the same problem as you using Gradle 2.1 and went back to Gradle 1.8. After doing so Gradle informed me this was unnecessary:

"The groovy configuration has been deprecated and is scheduled to be removed in Gradle 2.0. Typically, usages of 'groovy' can simply be replaced with 'compile'. In some cases, it may be necessary to additionally configure the 'groovyClasspath' property of GroovyCompile and Groovydoc tasks."

I upgraded to Gradle 2.2, and running Gradle tasks were successful after changing 'groovy' dependency configs to 'compile'. I tried with both the wrapper and the native install of gradle.

Presumably Gradle 2.1 would have also worked; I stayed with 2.2 since I already put forth the effort of installing it (originally in the hopes that 2.1 -> 2.2 was the solution.)

from jenkins-build-per-branch.

tknerr avatar tknerr commented on July 16, 2024

More output with --stacktrace and --debug:
https://gist.github.com/tknerr/5314611de7ef30339eb4

from jenkins-build-per-branch.

tknerr avatar tknerr commented on July 16, 2024

I seem to get past that error by using Gradle 1.12 instead of 2.0

from jenkins-build-per-branch.

tknerr avatar tknerr commented on July 16, 2024

Solution: use Gradle 1.x :-)

from jenkins-build-per-branch.

mukeshkamboj avatar mukeshkamboj commented on July 16, 2024

@tinyrye
I am new to gradle. There is below line in dependencies block in build.gradle file.

groovy 'org.codehaus.groovy:groovy:2.2.1'

Why do we require this. This is breaking build with gradle 2.2.1 version. What is the use of it and alternative of it.

Please point me to the link where i can study this.

from jenkins-build-per-branch.

mcordone avatar mcordone commented on July 16, 2024

I know this is a little bit old but getting same error using Gradle 2.3 or 2.7, is this issue has ever been address? any solution?

Thanks

from jenkins-build-per-branch.

voidabhi avatar voidabhi commented on July 16, 2024

+1

from jenkins-build-per-branch.

jamesdh avatar jamesdh commented on July 16, 2024

It's a legacy declaration for using groovy in earlier Gradle 1.x versions. That's why it's good practice to include the gradle wrapper in gradle projects, and hence why it's suggested to use gradlew within this project while running it as opposed to your local host systems installation of gradle.

from jenkins-build-per-branch.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.