Skip to content
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

The common-util: Fixed dependencies on default charset #25119

Merged
merged 1 commit into from
Aug 28, 2024

Conversation

dmatej
Copy link
Contributor

@dmatej dmatej commented Aug 26, 2024

  • The asenv.conf file must be UTF-8 by default - it is provided by us.
  • Property files are Latin1 aka ISO-8859-1 by default.
  • ProcessStreamDrainerWorker still uses default charset but was formatted.
  • XmlParserHelper was not used so I deleted it
  • FileUtils
    • Explicit usage of GC allowed here
    • Fixed dependencies on system default charset - added parameter
    • However line endings are still taken from system; it is ok for all actual usages (PEM file allows CRLF, CR, LF, pid file doesn't have line ending) and I added that to javadoc.
  • PayloadImpl now converts string to utf8 byte array, not system default charset
  • ServerDirs - local paswordfile is UTF-8 encoded, not system default charset
  • SSHUtil - PEM files use Latin1 and all types of line endings are allowed.
  • AsadminInput - still use system defaut charset. Controversial.
  • FileRealmHelper - Using UTF-8

@dmatej dmatej added this to the 7.0.17 milestone Aug 26, 2024
@dmatej dmatej requested review from arjantijms and avpinchuk August 26, 2024 19:52
@dmatej dmatej self-assigned this Aug 26, 2024
@dmatej dmatej marked this pull request as draft August 26, 2024 21:02
- The asenv.conf file must be UTF-8 by default - it is provided by us.
- Property files are Latin1 aka ISO-8859-1 by default.
- ProcessStreamDrainerWorker still uses default charset but was formatted.
- XmlParserHelper was not used so I deleted it
- FileUtils
  - Explicit usage of GC allowed here
  - Fixed dependencies on system default charset - added parameter
  - However line endings are still taken from system; it is ok for all actual
    usages (PEM file allows CRLF, CR, LF, pid file doesn't have line ending)
    and I added that to javadoc.
- PayloadImpl now converts string to utf8 byte array, not system default charset
- ServerDirs - local paswordfile is UTF-8 encoded, not system default charset
- SSHUtil - PEM files use Latin1 and all types of line endings are allowed.
- AsadminInput - still use system defaut charset. Controversial.
- FileRealmHelper - Using UTF-8


Signed-off-by: David Matějček <[email protected]>
@dmatej dmatej force-pushed the common-util-vs-spotbugs branch from 540bd11 to 66d95bc Compare August 27, 2024 08:23
@dmatej dmatej marked this pull request as ready for review August 27, 2024 09:38
@dmatej dmatej merged commit 1e81265 into eclipse-ee4j:master Aug 28, 2024
2 checks passed
@dmatej dmatej deleted the common-util-vs-spotbugs branch August 28, 2024 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants