-
Notifications
You must be signed in to change notification settings - Fork 159
coverageAggregate creates incorrect links #69
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
Comments
I am also running into this issue. All of the links work for the sub-projects browsed individually, but as mentioned break in the aggregated version. As a note, I am running 1.0.1 |
I'm also being affected by this when trying 1.0.1 |
I have just found the same issue. However, to me the problem is that the link to the
should be (without leading
So it would seem that the |
Try resolvers ++= Seq( Classpaths.sbtPluginSnapshots, Resolver.sonatypeRepo("snapshots") )
addSbtPlugin("org.scoverage" % "sbt-scoverage" % "1.0.5-SNAPSHOT") to your |
Is there an ETA on when the official 1.0.5 version will be released? The aggregate reporting fix is working great in the snapshot release. |
This is fixed now, I think. |
I believe this should be fixed now. If this is still an issue, please do report back. |
[issue originally reported in [Issue #13 ]]
I can confirm that the link to the sub-project's files are broken.
For example:
should be instead:
is it possible that the path is taken from the XML (apart from the
.html
suffix, the path used resolves to the actual location of the.scala
file)?Cursorily browsing around, it would appear to me that the simplest fix would be to bring in everything from the sub-project's
scoverage-report
folder into the top-level project's folder, apart from theindex.html
,overview.html
andpackages.html
- in the XML the refs to the source files are correct, and then adjust the links to the files.The text was updated successfully, but these errors were encountered: