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

Drop support for separate coverage reports #839

Closed
vilchik-elena opened this issue Nov 24, 2017 · 3 comments · Fixed by #840
Closed

Drop support for separate coverage reports #839

vilchik-elena opened this issue Nov 24, 2017 · 3 comments · Fixed by #840
Assignees
Milestone

Comments

@vilchik-elena
Copy link
Contributor

vilchik-elena commented Nov 24, 2017

Since SonarJS 4.0 stop supporting these properties

  • sonar.javascript.forceZeroCoverage
  • sonar.javascript.lcov.reportPath
  • sonar.javascript.lcov.itReportPath
@vilchik-elena
Copy link
Contributor Author

relates to #837

@vilchik-elena vilchik-elena added this to the 4.0 milestone Nov 24, 2017
@ghost ghost assigned vilchik-elena Nov 24, 2017
@vilchik-elena vilchik-elena changed the title Drop support for separate coverage report Drop support for separate coverage reports Nov 27, 2017
@NilSet
Copy link
Contributor

NilSet commented Nov 29, 2017

Will SonarJS create its own coverage reports instead of importing lcov?
Edit: Never mind, I see those are redundant properties, and I assume sonar.javascript.lcov.reportPaths will remain.

@vilchik-elena
Copy link
Contributor Author

@NilSet indeed

@ghost ghost removed the review label Nov 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants