Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gradle reports NO-SOURCE instead of UP-TO-DATE #18

Open
sherter opened this issue Apr 14, 2017 · 0 comments
Open

Gradle reports NO-SOURCE instead of UP-TO-DATE #18

sherter opened this issue Apr 14, 2017 · 0 comments

Comments

@sherter
Copy link
Owner

sherter commented Apr 14, 2017

Since v3.4 Gradle reports NO-SOURCE instead of UP-TO-DATE when everything is already formatted properly. This is due to our own caching mechanism, which injects the files that need to be formatted into the task right before the task is executed (the gradle caching mechanism doesn't allow us to tell that a file is up-to-date if it was changed in the first run). Functionality is not influenced by this in any way, but users might be irritated by this message. Let's see if we can somehow trick Gradle into reporting UP-TO-DATE instead...

@sherter sherter changed the title Gradle reports NO-SOURCE instead of UP-TO-DATE ( Gradle reports NO-SOURCE instead of UP-TO-DATE Apr 14, 2017
Repository owner deleted a comment from praveenraja21 Mar 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant