-
Notifications
You must be signed in to change notification settings - Fork 16
JACOCO-74 Import coverage for files whose name and package clashes across different nested modules #156
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
This simple project that produces an aggregate report when running `mvn verify sonar:sonar` should correctly produce coverage information on 1 file covered by a test in another sub project.
Add a sub project isolated from the aggregate report coverage to see how both sensor can work on the same project.
4720aa4 to
1a27e20
Compare
1a27e20 to
c9c318c
Compare
9327fb9 to
7678a81
Compare
leonardo-pilastri-sonarsource
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would be more comfortable with a windows build/qa on the CI as well, but since we did not introduce anything new in terms of paths manipulation, I'll just create a separate ticket for that. This one looks good to me 👍
|




No description provided.