Manos Batsis wrote:
Having all files stick to a given (default) encoding will mean a nightmare
to all
platforms where such encoding is not the system one when it comes to
modifying or > editing files.
I can't follow your arguments here. Proper text editors allow you to select
the file encoding you save your files in, so the system default encoding
should not matter.
we should deprecate any file operation that fails stating an explicit
encoding and this way encourage users to explicitly state the encoding in
use.
I'm not sure what you mean with "file operation".
We have feature requests out for PMD and Checkstyle to detect usage of
problematic IO APIs like java.io.FileReader and I know that already some
work on these has been started.
As for the Maven plugins themselves and their file handling: We don't need
to deprecate things here. Every plugin that reads/writes plain text files
should offer an encoding parameter for the user to configure the correct
file encoding. Work on extending unconfigurable plugins with such a
parameter is in progress/scheduled.
c) a) + discourage any use of files that do not state encoding explicitly
I take this as a vote for a) with the intention to output a warning in case
the encoding was not specified. Please correct me if I misunderstood you.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
