[jboss-jira] [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:
----------------------------------
Oh, lordy, lordy, the universe makes sense! Thank you DML!
Ondrej, the working versions of Remoting 2 come from
https://svn.jboss.org/repos/jbossremoting/remoting2/branches/2.2 (versions 2.2.x) and
https://svn.jboss.org/repos/jbossremoting/remoting2/branches/2.x (versions 2.4.x and
2.5.x). https://svn.jboss.org/repos/jbossremoting/remoting2/trunk got lost in the fog of
war in prehistorical times. Ignore.
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