Compilation errors are not shown and highlighted with red next to the line automatically after build as they are in regular Eclipse project or in Maven Eclipse project. Spring-Eclipse team says the Gradle API must be updated to support this. Please provide a way for this integration to be built. For me this manual refresh stuff every time makes the Eclipse integration pretty much not workable. The whole point of a tool is that it should handle things automatically at the right times.

Key: STS-1967
Issue Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: David Oliver
Environment:

Windows Vista 64-bit running 32-bit STS

Operations
View all
View comments
View history

Gradle Eclipse integration does not show errors on files in editor or navigator/package explorer
Updated: 27/Jul/11 5:03 PM Created: 27/Jul/11 12:09 AM

The following comment has been edited on this issue: [ Permalink ]
Author: Kris De Volder
Created on: 27/Jul/11 5:03 PM
Edited by: Kris De Volder
Edited on: 27/Jul/11 5:04 PM
Comment:

You should get errors after you refresh dependencies. You have to do this manually from the Gradle context menu.

There are a few reasons for this:

refresh dependencies is (or can be) very time consuming
Gradle API doesn't provide any info yet about when the information in the Gradle model needs updating.

Clean and build will not cause errors, since you will just keep rebuilding with the dependencies that where cached. This cache is only flushed by a refresh dependencies. (Even if you restart Eclipse, the depencies are persisted because otherwise it can cause a rather long delay before the IDE becomes responsive / useable after startup).

was:

You should get errors after you refresh dependencies. You have to do this manually from the Gradle context menu.

There are a few reasons for this:

refresh dependencies is (or can be) very time consuming
Gradle API doesn't provide any info yet about when the information in the Gradle model needs updating.

Clean and build will not cause errors, since you will just keep rebuilding with the dependencies that where cached. This cache is only flushed by a refresh dependencies. (Even if you restart Eclipse, the depencies are persisted because otherwise it puts an can cause a rather long delay before the IDE becomes responsive / useable after startup).

Project: SpringSource Tool Suite
Components: GRADLE
Affects Versions: 2.7.1.RELEASE
Labels: gradle

Description

1. Download latest Springsource Tools Suite, springsource-tool-suite-2.7.1.RELEASE-e3.7-win32-installer
2. Install gradle extension
3. Import a gradle project with dependencies and source files that import and use those package dependencies
4. Comment out dependencies in the Gradle build file
5. Clean and build

I would expect that the build would fail, the import statements referring to those dependencies and the objects using those dependencies should be highlighted in red when editing the file in Eclipse and the navigator/package explorer hierarchy should show red x's next to the files that did not compile successfully. None of that happens.

The gradle build actually succeeds even after I refresh my resources in Eclipse. I then go out to the windows command window outside of eclipse and run a clean build there at that point I finally see an error. When I return to Eclipse and run the clean build again, I do see errors in the console window from the Eclipse build which is good. However, Eclipse still does not show any red x's next to files that failed to compile, and it does not show inside the files in the file editor the lines that failed to compile with any red x's next to those lines - instead the files look as if they still compiled properly.

I'm using a top level gradle project that builds 2 subprojects.