Brian E. Fox wrote:
I'd say based on the various points brought up by the users that platform
encoding as the default makes the most sense.
Yes, that's the majority's sense. I counted roughly but so far the ratio of
votes is about 3:1 for keeping platform encoding as default vs. Latin-1,
taking together the votes on the user list and over on the wiki.
Given that the thread on the user list is already quite idle, I believe
their is no need in waiting much longer for further votes, in particular I
don't expect a complete turnaround of the already clear direction. So
tomorrow (or the day after, depending whether SVN will be alive), I would
like to start adopting the plugin sources to
- have their encoding parameter default to null, meaning platform encoding
as before
- output a warning message if the encoding is unspecified
This warning would simply check whether the encoding parameter is null. As a
side-effect, people that absolutely don't care about encoding and don't want
Maven to output a warning can simply set the parameter to ${file.encoding}
which is non-null but still has the same effect of using the platform
encoding.
Agreed?
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
