Git Product home page Git Product logo

Comments (5)

kdvolder avatar kdvolder commented on March 29, 2024

The question is whether this is a bug in the STS tooling, the gradle tooling API, the tomcat plugin or gradle itself.

The first thing to try is if you get a similar error doing the same thing on the commandline. e.g try to generate eclipse metadata on the commandline with the 'gradle eclipse' plugin by running tasks './gradlew cleanEclipse eclipse'.

While not exactly the same, this is probably the closest you can get to doing the 'build model' step in the tooling from the commandline.

from eclipse-integration-gradle.

kdvolder avatar kdvolder commented on March 29, 2024

BTW: I have hunch maybe the tomcat plugin might not be compatible with the version of Gradle you are trying to run it with. The stacktrace suggest an API incompatiblity (i.e. someone is calling a method that doesn't exist).

from eclipse-integration-gradle.

rkapsi avatar rkapsi commented on March 29, 2024

gradle cleanEclipse eclipse works.

You're most likely correct regards Gradle version. We're using Gradle 1.6+. Some folks had an older version installed and ran into the same problem on the CLI as the Tomcat Plugin (I believe I saw it was downloading Gradle 1.5 in the Build Model step).

from eclipse-integration-gradle.

kdvolder avatar kdvolder commented on March 29, 2024

Okay, in that case I suggest you use the gradle wrapper on your project. If the wrapper properties are present. The tooling API will use the gradle version they stipulate. That way you won't have an issue with using the wrong gradle version.

The problem you are hitting is because Gradle tooling API we use is still at 1.5 you end up using 1.5 by default.

If you add the gradle wrapper and set it to use 1.6 then the tooling API will use 1.6 and the problem will go away.

It is generally a good idea to add the wrapper to your project to explicitly define what version of gradle it should use.

Otherwise you are just taking your chances with the default.

I'm closing this issue as it seems there's no bug here :-)

from eclipse-integration-gradle.

rkapsi avatar rkapsi commented on March 29, 2024

Adding a wrapper task and pointing it to 1.6 did the trick.

from eclipse-integration-gradle.

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.