-
Notifications
You must be signed in to change notification settings - Fork 3
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
Nothing gets aggreated. #2
Comments
It seems that it looks for See Line 36 in 42b6e83
It already been 2 years ago since I worked on this gradle plugin, but several customers are using this gradle plugin to generate these reports. And you´re right I unfortunately hard coded the file name to be Do you have a sample project, where it can be tested? Unfortunately I do not have access to the customers using this plugin any more... |
I wonder if you're basing this off of an older version of spotbugs? Itd efinitely makes the files in build\reports\spotbugs\main.xml \ test.xml |
I have same issue with aggregation as @stealthrabbi. What @stealthrabbi mentioned about default report location and name is correct. After reading your code, I understand the plugin is expecting spotbugsXml.xm in subfolders of rootDirectory. So I renamed my main.xml to spotbugsXml.xm and put it in multiple level of its sub folders. None works. File SpotBugsAggregated.xml was generated in rootDirectory by Gradle task 'aggregateSpotBugsFiles'. But its content is like below that has no real data My build.gradle file sitting in rootDirectory is like below (only spotbugs related content is listed) ==== partial of build.gradle related to spotbugs ======= subprojects {
} I feel like it might be the issue with xml file. So I attached a short version of my spotbugsXml.xml. It has all the ingredients but with less data. (Have to rename to spotbugsXml.txt for upload). |
THe default names of spotbugs files is main.xml, test.xml. This plugin doesn't find those files according to the documentation, nor does there seem to be a way to change what files it looks for.
The text was updated successfully, but these errors were encountered: