Open beamerblvd opened 5 years ago
Thanks for opening your first issue here! :smiley: Please check our contributing guideline. Especially when you report a problem, make sure you share a Minimal, Complete, and Verifiable example to reproduce it in this issue.
I did resolve my issue, but I still feel there's a bug here. I changed <excludeBugsFile>
to <excludeFilterFile>
. It was originally <excludeFilterFile>
, but I had changed it to <excludeBugsFile>
at some point because it wasn't working and I couldn't figure out why. Apparently, I solved whatever problem that was, but <excludeBugsFile>
created a new problem for me.
I think there are two problems here:
<excludeBugsFile>
should have explained what the parsing problem was. That might have clued me in what I had done.<excludeBugsFile>
and <excludeFilterFile>
.Could you try to remove the comment at the beginning of your XML file? It could be problem because it makes two root elements in one file.
What content? Are you talking about the comment? I did already try removing that without success, but it definitely does not make two root elements in one file. As I said in my comment above, I fixed it by changing <excludeBugsFile>
to <excludeFilterFile>
, so I think the actual problem is that <excludeBugsFile>
is looking for a different schema. But the documentation doesn't explain what <excludeBugsFile>
is, and the Dom4j error doesn't explain how that file violates the schema.
Got it, thanks. You mean we need to update official guide for Maven plugin, right?
For 2, I think it is better to transfer this issue to Maven plugin project, I'll handle it. For 1, I will make a separated issue in this repo.
@KengoTODA In the link you provided, I assume the fact that all the auto generated maven help there is blank. Is that the case? If so, I tried a few things to make the code show up but no luck. I'm not sure why it's not pulling javadocs other than possibly that this is groovy. I did make some adjustments though so the groovy docs work again and those are accessible on the site. However, that isn't quite what we want :(
I'm also not sure why plugin doesn't refer existing javadoc ;(
I too am struggling on this. Nothing I do seems to get spot-bugs to load the XML file. I cannot figure out why without additional logging.
Finally figured it out. I found an errant <excludeBugsFile>
configuration item instead of <excludeFilterFile>
I'm using SpotBugs 3.1.8 via the
spotbugs-maven-plugin
3.1.8. I'm getting the following error. Unfortunately, this output is with maximum debug/traces turned on. There is no other information. Nothing at all indicates what's wrong with my file.I've confirmed that it's not a matter of it not finding the file, because I changed the configured name of the file and I got a different error (that the name couldn't be found). So it is definitely finding my file, it just can't parse it and won't tell me why.
Here is my plugin configuration:
Here is my
spotbugs-exclude.xml
file:I have no idea what the problem here is, but there is definitely a bug, and it's one of the following:
For what it's worth, I have tried taking the
xmlns
/xsd
stuff out of the file, and it made no difference.