Jochen Wiedmann wrote:
I'd opt for
c) Use a configurable value, by default the current platform encoding.
To my understanding, that's nothing more than variant a). Of course, we are
talking about a configurable value. Locking down plugins to any kind of
encoding without having a chance of customization would be a design flaw par
excellence.
Some day in the future, each and every plugin should offer a configuration
parameter to control the encoding for its input/output files. So that is the
finest grained control with regard to configuration. Next up, we are
planning on a central POM property/element where users specify the file
encoding for all their plugins. The already mentioned wiki article outlines
this in more detail.
This thread is only about the situation in which a user did *not* configure
the encoding but expects the build to use some default value. Taking this
default from the platform or from an established convention is the remaining
question.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
