[GRADLE-2105] Cannot specify jvm args to Findbugs Created: 15/Feb/12 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 1.0-milestone-8 |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | Paul Jimenez | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 4 |
Description |
Findbugs will OOM with default jvm args when faced with a sufficently large codebase. The ant.findbugs() call will take a jvmargs: ... argument to fix this.. but such is not exposed by the findbugs plugin. |
Comments |
Comment by Justin Ryan [ 23/Mar/12 ] |
I'm adding some other optional parameters to the findbugs tasks. Is there any issue with also adding jvmargs? Or is there something in the gradle pipeline which would preclude this? E.g. running findbugs inside the current JVM? |
Comment by Daniel Gredler [ 09/Jan/14 ] |
Currently having trouble figuring out how to do this: |
Comment by Benjamin Muschko [ 15/Nov/16 ] |
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
Comment by Benjamin Muschko [ 10/Feb/17 ] |
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved. |