Skip to content

Scoverage HTML report may fail to render #62

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

Closed
mauhiz opened this issue Oct 15, 2014 · 4 comments
Closed

Scoverage HTML report may fail to render #62

mauhiz opened this issue Oct 15, 2014 · 4 comments

Comments

@mauhiz
Copy link

mauhiz commented Oct 15, 2014

Because classpath is flattened, getResource("/index.html") will pick any index.html on the root of the classpath. In my particular issue, it was a index.html bundled in specs2.

It is easy to avoid such name collisions, just by putting the resources in a subfolder e.g src/main/resources/scoverage/index.html.

@sksamuel
Copy link
Member

Makes sense. Will fix thanks.
On 15 Oct 2014 02:53, "Vincent PÉRICART" [email protected] wrote:

Because classpath is flattened, getResource("/index.html") will pick any
index.html on the root of the classpath
https://github.com/scoverage/scalac-scoverage-plugin/blob/master/src/main/scala/scoverage/report/ScoverageHtmlWriter.scala#L18.
In my particular issue, it was a index.html bundled in specs2.

It is easy to avoid such name collisions, just by putting the resources in
a subfolder e.g src/main/resources/scoverage/index.html.


Reply to this email directly or view it on GitHub
#62.

@cleverdeveloper
Copy link

After Play 2.3.6 was released now Specs2 "index.html" file is written instead of scoverage report when using with Play.

@sksamuel
Copy link
Member

sksamuel commented Nov 5, 2014

Will be fixed in release 0.99.11 which I am prepping now.

@gslowikowski
Copy link
Member

@cleverdeveloper Where (in which jar file) is this "index.html" file? I don't see it.

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

No branches or pull requests

4 participants