Skip to content
This repository has been archived by the owner on Jul 9, 2022. It is now read-only.

Mark Gradle's build directories as derived resources #111

Closed
tbrannt opened this issue Dec 29, 2017 · 3 comments
Closed

Mark Gradle's build directories as derived resources #111

tbrannt opened this issue Dec 29, 2017 · 3 comments

Comments

@tbrannt
Copy link

tbrannt commented Dec 29, 2017

Reopening https://jira.spring.io/browse/STS-2832

By default the command-line gradle outputs to the project's build directory. The default Eclipse output is the bin directory. These should remain separate.

The Eclipse resource view includes the compiled files in the build directory. It would improve the usability if these directories were marked as "derived" when importing a project.

The workaround [1] of rewriting the project file to add resource filters is error prone and resulted in STS-2822. It would be nice if this was part of the plugin instead.

[1] http://forums.gradle.org/gradle/topics/eclipse_generated_files_should_be_put_in_the_same_place_as_the_gradle_generated_files

I came across the exact problem described in STS-2832 while using buildship. However this issue was closed with a hint to reopen it here.

@martinlippert
Copy link
Contributor

We do only minimal maintenance work on this project at the moment and users should migrate over to use Buildship instead.

Therefore I am not exactly sure what you mean with your comment above about already using Buildship and coming across this problem, too. Is this a problem when using Buildship? Can you post a link to the discussion that you mentioned above (about the hint to post here), so that I can follow up there, too?

@paulvi
Copy link
Contributor

paulvi commented Dec 29, 2017

@tbrannt Buildship issues are at https://github.com/eclipse/buildship

@tbrannt
Copy link
Author

tbrannt commented Dec 29, 2017

Sorry, intended to open this in the buildship repo

@tbrannt tbrannt closed this as completed Dec 29, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

3 participants