Skip to content
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

New configuration: Skip project/submodule that are not compiled #56

Closed
h3xstream opened this issue Oct 11, 2016 · 5 comments
Closed

New configuration: Skip project/submodule that are not compiled #56

h3xstream opened this issue Oct 11, 2016 · 5 comments

Comments

@h3xstream
Copy link
Member

Regarding this situation #46, the most accommodating option would be to have an option to ignore missing compiled code.

Since the validation is needed for 99.9% of projects, it should not be enable by default.

@lolnoob
Copy link

lolnoob commented Nov 7, 2016

I have some java code in the project which requires only static analysis and is never build. Hence the need for Findbug disables SQ analysis of my project.
Do you have any idea on when this enhancement may be introduced to the plugin?

@acartapanis
Copy link

acartapanis commented Dec 26, 2017

Sorry but to me this is not an enhancement, this is a bug.
I have a huge project with many resources-only jar, and I cannot use sonarqube on it for now.
The only way to make my project analyzable is to remove the findbugs plugin, wich is sad to me.
Is there a solution to keep the findbugs plugin enabled with resources-only projects ?

@hohwille
Copy link

I am facing the same issue. I do have projects with packaging jar or war but no single Java class. Then this plugin fails and I can not do the sonar analysis if findbugs is activated.

E.g. a simple example is a project where I do have a spring boot application that I want to build as a regular JAR in order to still use it as a regular dependency but then I also need another module of packaging war that simply converts the JAR into a bootified WAR. This project does not have a single Java class and hence it fails with

[WARNING] Findbugs needs sources to be compiled. Please build project before executing sonar or check the location of compiled classes to make it possible for Findbugs to analyse your (sub)project (...).

Example:
https://github.com/oasp/my-thai-star/tree/develop/java/mtsj

@hohwille
Copy link

Already according to the logged message this is a bug:

  • all sources are compiled (if there are no sources)
  • I did build the project before executing sonar so also the suggested hint is wrong.

h3xstream added a commit to h3xstream/sonar-findbugs that referenced this issue Mar 14, 2018
@h3xstream
Copy link
Member Author

Implemented

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants