Benjamin Bentmann wrote:
A controversial aspect of this proposal is which file encoding should be
assumed in case the user did not specify this in the POM. This poll should
help us to come to a well-founded decision.
These are the two possible directions to go:
a) Use the current platform encoding, aka the system property
"file.encoding".
b) Use a static/fixed value that is defined by convention, i.e. is not
platform-dependent.
More than 24 hours after the last response on this thread, I believe it's
fair to say the die is cast. The votes here on this thread on over on the
related wiki article sum up to almost 90% for approach a) which is a rather
clear outcome. I will update our proposal accordingly.
Unfortunately, the change for MJAVADOC-165 was already released, i.e. the
Javadoc Plugin 2.4 uses Latin-1 as default encoding if its configuration
does not specify otherwise. As a matter of consistency, this should be
reverted to use platform encoding, however this would imply another breaking
change. Given the apparent dilemma, I created MJAVADOC-185 where users can
vote for this change if it should happen.
I would like to thank everybody who participated in this poll and shared his
thoughts.
Benjamin Bentmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
