[jboss-remoting-issues] [JBoss JIRA] (JBREM-1286) Fix sources encoding to UTF-8
[
https://issues.jboss.org/browse/JBREM-1286?page=com.atlassian.jira.plugin...
]
Ron Sigal commented on JBREM-1286:
----------------------------------
Hey Ondrej,
I don't see how this problem occurs. The original text in CallbackStore.java is
{quote}
Key for setting the file suffix to use for the callback objects written to disk. The
default value is "ser".
{quote}
in a javadoc comment. I don't get the "unmappable character for encoding
UTF-8" message when I build the project, and I don't see it when the project
builds in jenkins.
Can you describe where you are seeing the message, or how to reproduce it?
Thanks.
Fix sources encoding to UTF-8
-----------------------------
Key: JBREM-1286
URL: https://issues.jboss.org/browse/JBREM-1286
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.2.4, 2.5.4.SP2
Reporter: Ondrej Zizka
Assignee: Ron Sigal
Fix For: 2.2.4.SP1, 2.5.4.SP4
I Ron, is it possible to fix this? It's really annoying to care about it in
environments like Hudson.
Compiling 395 source files to build/classes
src/main/org/jboss/remoting/callback/CallbackStore.java:79: unmappable character for
encoding UTF-8
* Key for setting the file suffix to use for the callback objects written to disk.
The default value is �ser�.
src/main/org/jboss/remoting/callback/CallbackStore.java:79: unmappable character for
encoding UTF-8
* Key for setting the file suffix to use for the callback objects written to disk.
The default value is �ser�.
2 errors
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira