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 logging #48

Closed
deedoubledub opened this issue May 15, 2019 · 2 comments
Closed

Gradle logging #48

deedoubledub opened this issue May 15, 2019 · 2 comments
Assignees

Comments

@deedoubledub
Copy link

The gradle daemon outputs logs to ~/.gradle/daemon/\<version\>/*.out.log. These logs quickly grow out of control to hundreds of megabytes or gigabytes in size. Please implement a procedure to suppress or cleanup these logs.

Upstream issue: gradle/gradle#2688
Example cleanup: https://discuss.gradle.org/t/gradle-daemon-produces-a-lot-of-logs/9905

@gkapfham
Copy link
Contributor

Thanks for raising this issue @deedoubledub. @Michionlion is it important to note that the example cleanup link provided suggests a solution involving the code that would go in the build file itself. This means that it is something that we would introduce to a build file for a sample assignment (or, as talked about a long time ago, something that GatorGrader knows how to generate). Do you know of a way in which we can easily integrate this into the Gradle plugin itself?

@gkapfham gkapfham pinned this issue May 24, 2019
@Michionlion
Copy link
Member

As noted above, this is an issue endemic to Gradle itself, and fixes would require changes to a user's build.gradle file. As such, no fix is planned for GatorGradle.

@Michionlion Michionlion unpinned this issue Jul 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants