Using classes and methods that rely on the default system encoding can result in code that works fine in its "home" environment. But that code may break for customers who use different encodings in ways that are extremely difficult to diagnose and nearly, if not completely, impossible to reproduce when it's time to fix them.
This rule detects uses of the following classes and methods:
* ``++FileReader++``
* ``++FileWriter++``
* String constructors with a ``++byte[]++`` argument but no ``++Charset++`` argument
** ``++String(byte[] bytes)++``
** ``++String(byte[] bytes, int offset, int length)++``
* ``++String.getBytes()++``
* ``++String.getBytes(int srcBegin, int srcEnd, byte[] dst, int dstBegin)++``
* methods from Apache commons-io library which accept an encoding argument when that argument is null, and overloads of those methods that omit the encoding argument