Open romani opened 5 years ago
@romani I'd like to see the plugin run with overridden dependency 3.1.5 to vet the issue is the plugin or with spotbugs itself. Given the stack trace, it would seem it is with spotbugs rather than the plugin.
to confirm, do you want to see log of build when it was 3.1.5 ? I tried to open issue on library itself but requires precise test case to reproduce ... not sure how to make it.
version definition : https://github.com/checkstyle/checkstyle/blob/master/pom.xml#L204
here is log on 3.1.5 - https://travis-ci.org/checkstyle/checkstyle/jobs/412242219#L758
Still use 3.1.6 plugin, add dependencies section for spotbugs 3.1.5. That way it downgrades spotbugs but otherwise runs plugin as is. I believe the issue is with spotbugs not this plugin and that will prove the theory and help get the issue over to code spotbugs team.
Get Outlook for Androidhttps://aka.ms/ghei36
From: Roman Ivanov notifications@github.com Sent: Wednesday, September 5, 2018 9:08:29 AM To: spotbugs/spotbugs-maven-plugin Cc: Jeremy Landis; Comment Subject: Re: [spotbugs/spotbugs-maven-plugin] mvn clean spotbugs:check give not errors (#75)
to confirm, do you want to see log of build when it was 3.1.5 ? I tried to open issue on library itself but requires precise test case to reproduce ... not sure how to make it.
version definition : https://github.com/checkstyle/checkstyle/blob/master/pom.xml#L204
here is log on 3.1.5 - https://travis-ci.org/checkstyle/checkstyle/jobs/412242219#L758
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/spotbugs/spotbugs-maven-plugin/issues/75#issuecomment-418723965, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AA7ho4NpoW5Qd-XBncS6rEpYbVUym4mWks5uX8zNgaJpZM4WUY0N.
Isn't this the expected behavior? SpotBugs operates on bytecode, and so it requires compiled classes. Doesn't mvn clean compile spotbugs:check
fix the problem for you?
yes, adding compile
works.
But should be there some warning or error ? that no bite code is found, validation is skipped.
I agree that a warning would not be unreasonable in such a scenario. It would also be great if the requirement of compiled classes was made clear in the plugin docs
Maybe extra property to fail if no binaries are found, in case config of compiler and spotbugs is unsynched.
steps: