[GRADLE-2109] FindBugs plugin on Windows fails on projects with many source files due Created: 16/Feb/12  Updated: 04/Jan/13  Resolved: 23/Apr/12

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-8
Fix Version/s: 1.0-rc-1

Type: Bug
Reporter: Brant Bobby Assignee: René Gröschke (Inactive)
Resolution: Fixed Votes: 3

Attachments: Text File command.txt    

 Description   

The FindBugs Gradle plugin fails when analyzing a Java project that contains enough .java and .class files to push the resulting command over the 8191-character limit (http://support.microsoft.com/kb/830473/)

13:06:31.291 [ERROR] [org.gradle.api.internal.project.ant.AntLoggingAdapter] [ant:findbugs] java.io.IOException: Cannot run program "C:\Program Files\Java\jdk1.6.0_30\jre\bin\java.exe": CreateProcess error=206, The filename or extension is too long

One partial workaround for this would be to configure the ant task to point to a JAR instead of a collection of .classes, although there's still the issue of the huge list of source files. In either case, the findbugs plugin exposes no way of doing this.



 Comments   
Comment by Peter Niederwieser [ 16/Feb/12 ]

Thanks for reporting this. We are aware of the problem.

Comment by René Gröschke (Inactive) [ 23/Apr/12 ]

this was fixed together with GRADLE-2167

Generated at Wed Jun 30 12:13:01 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.