Use fully-qualified class names to avoid ambiguity in reports #138
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(Fixes scalac-scoverage-plugin/scoverage#27)
RichardBradley
force-pushed
the
issue-27
branch
from
5ed4553 to
fc579c0
Compare
|
Now rebased and ready to merge |
sksamuel
added a commit
that referenced
this pull request
Dec 2, 2015
Use fully-qualified class names to avoid ambiguity in reports
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(Fixes scoverage/scalac-scoverage-plugin#27)
(Conflicts with #133 only in the version numbers, I think. Both PRs need a
sbt-scoverageversion number increment. I have chosen different version numbers for the two PRs to avoid confusion.)