-
Notifications
You must be signed in to change notification settings - Fork 90
chore: Support spotbugs running anywhere #1537
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
Conversation
💾 Artifacts Size Report
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## v2 #1537 +/- ##
=====================================
Coverage ? 87.21%
Complexity ? 530
=====================================
Files ? 61
Lines ? 1854
Branches ? 230
=====================================
Hits ? 1617
Misses ? 163
Partials ? 74 ☔ View full report in Codecov by Sentry. |
|
If I understand correctly, it's not only spotbugs but also checkstyle, licence-header is for checkstyle, spotbugs-exclude for spotbugs |
@jeromevdl exactly, it covers all of this! |
Issue #, if available: n/a
Because spotbugs relies on a relative path to find its configuration and license-header, you can't run
mvn install
from arbitrary subdirectories in the project successfully. For instance -powertools-parameters
-mvn install
will fail here with an inability to find thelicense-header
file. Thismaven.multiModuleProjectDirectory
variable only gets set to the actual project root if a .mvn directory exists.By doing this we can easily use it to find files relative to the root without having to specify some relative path property in every single POM.
Checklist
Breaking change checklist
RFC issue #:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.