Timeline for Encoding in Maven Tests not working properly
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 14, 2022 at 20:44 | answer | added | Missael De Nadai | timeline score: 1 | |
| Nov 2, 2021 at 9:31 | answer | added | JRr | timeline score: 3 | |
| Oct 4, 2018 at 7:39 | vote | accept | Yanick Salzmann | ||
| Aug 15, 2016 at 13:21 | answer | added | Yanick Salzmann | timeline score: 36 | |
| Aug 15, 2016 at 11:07 | comment | added | Yanick Salzmann |
I also checked with a hex editor how the .java file looks and it seems to be UTF-8 encoded: String a = "öäü"; NFLAuth.sign(a); (for String a = "öäü"; NFLAuth.sign(a);)
|
|
| Aug 15, 2016 at 11:01 | comment | added | Yanick Salzmann |
Good idea, I did the following: NFLAuth.sign("\u00E4\u00F6\u00FC"); and within that method I printed the getBytes() of the input variable. IntelliJ: C3 A4 C3 B6 C3 BC Maven: E4 F6 FC So apparently it is not using UTF-8 encoding in Maven...
|
|
| Aug 15, 2016 at 10:53 | comment | added | Joop Eggen |
Try first u-escaped text, so as to check that the editor encoding equals the javac encoding: "\u00E4\u00F6\u00FC..." (äöü...). Especially as Windows-1252 would cover the letters too.
|
|
| Aug 15, 2016 at 10:39 | comment | added | Yanick Salzmann | I have added the POM | |
| Aug 15, 2016 at 10:39 | history | edited | Yanick Salzmann | CC BY-SA 3.0 |
added 4012 characters in body
|
| Aug 15, 2016 at 8:52 | comment | added | Prim |
Are you sure you added in your pom a property like this <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> ? If not, try to do this
|
|
| Aug 15, 2016 at 8:48 | comment | added | chrylis -cautiouslyoptimistic- | Post your POM. Are you sure you're using the right encoding for the compilation step? | |
| Aug 15, 2016 at 8:20 | history | asked | Yanick Salzmann | CC BY-SA 3.0 |