Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
FindBugs is unable to find classes in a multiflavored project
See original GitHub issueHi @vanniktech, thanks for the great plugin! I believe it will become very popular soon. There some issues, however, that prevent us from use it in production. Here is one of them.
Our project has a number of ABI flavors, like “arm” and “x86”. We found that it’s not possible to perform FindBugs check on it:
./gradlew findbugs
... assembles all flavours ...
:app:assemble
:app:findbugs FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:findbugs'.
> No classes configured for FindBugs analysis.
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED
That’s because it searches for classes to analyze in hardcoded place: https://github.com/vanniktech/gradle-code-quality-tools-plugin/blob/master/src/main/groovy/com/vanniktech/code/quality/tools/CodeQualityToolsPlugin.groovy#L158 , but in our project these classes are placed in a build/intermediates/classes/arm/debug .
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Created a separate issue: https://github.com/vanniktech/gradle-code-quality-tools-plugin/issues/68
Closing this. Have a look at #75 for the reasoning behind this.