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
java.nio.charset.UnmappableCharacterException: Input length = 1 #134
Comments
Hi guys, Do you have an estimate as to when the fix is going to be released? Thanks, |
@sksamuel Sam? |
I'll do a release tonight. |
Great, thanks! |
Is this issue fixed? Where/when? |
I missed this PR. It's late, but I must say, I don't like this solution. I would like to have possibility to parametrize source encoding. This is natural in all Maven plugins I'm using. I don't want to add warning to Scoverage Maven plugin, that |
Hi guys, Any updates on this ? Thanks, |
Here you have alternative approach - source encoding parametrized |
Very simple SBT plugin implementation - https://github.com/gslowikowski/sbt-scoverage/tree/source-encoding. |
scoverage/sbt-scoverage#86 is related to this issue and will be fixed, if my proposed solutions will be accepted. |
SBT plugin proposed implementation (https://github.com/gslowikowski/sbt-scoverage/commits/source-encoding) improved - default encoding value pulled from |
Nobody's interested in this functionality anymore? |
I've created new PR based on current code. |
PR for SBT ready - scoverage/sbt-scoverage#155 |
Maven version is still valid. |
If nobody objects, I will apply all PRs. |
Source encoding parametrization - fix for issue #134
PR merged, |
Source encoding parametrization - fix for issue scoverage/scalac-scoverage-plugin#134
|
I have some nice Slovak characters in source code. For example:
But then if I run Scoverage it crashes with following:
It is obviously related to encoding. I am able to reproduce it by explicitly setting wrong encoding in
CodeGrid.scala
line 63:Current implementation uses an arbitrary default encoding which is probably not ideal. It can be different for every one of us. I would propose to hardcode UTF-8. If you like this idea, I will send a pull request soon.
The text was updated successfully, but these errors were encountered: