I vote (a). Use UTF-8. I'd actually prefer an option under the <reporting> element to set the encoding to a desired value and have it default to UTF-8, but I can live with a procrustean solution.
-K Hervé BOUTEMY wrote: > > Dear community, > > The Maven team is currently discussing a proposal about the future > handling > of reporting output file encoding by the various plugins, please see our > wiki > article [0] for all details. > > 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 fixed UTF-8 encoding > > b) use same encoding as source files > > > Approach a) is simple and sould work for everybody, since any character > can be > output in UTF-8. > Approach b) is more subtle and mimics the behaviour of javadoc tool. Since > reports contain more data than source content, there are cases where this > default value won't be appropriate (for example, if project's description > in > pom.xml contains characters that can't be output with source files > encoding). > > > So, please let us know: > > [a] Use UTF-8 > [b] Use source files encoding > > Regards, > > > Hervé > > > [0] > http://docs.codehaus.org/display/MAVEN/Reporting+Encoding+Configuration > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/-POLL--Default-Value-for-Reports-Output-Encoding-tp18838502p18914675.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
