Brian E. Fox wrote:
Who exactly is asking for this change?
Basically only me, in an attempt to guarantee reproducible builds by eliminating a dependency on an environmental property.
Is there an issue with a huge number of votes attached to it?
To my knowledge, no. We have MNG-2216 that is quite similar to our proposal but has (excluding myself) only three other votes which is not that much. Let my point out that the encoding issue is subtle and I expect a fair amount of people that are simply not aware of it, i.e. their builds work just by coincidence.
This is certainly relevant when asking for a change as fundamental as this. If a handful of people have issues with this, but everyone else is ok with platform default, then this is an important deciding factor.
Of course user's sense is important but there is also the question where the PMC would like its baby to go. For example, I see parallels to the question whether the Maven 2.1 POM should require explicit versions for plugins. It would guarantee stable builds but no doubt there will be users complaining about the need to touch their POMs.
Anything we do that causes behavior changes will have to wait until 2.1, we simply cannot allow this kind of change in 2.0.x.
Please keep in mind that the default value for the file encoding is not only targetted at the Maven core. First of all, the change in behavior occurs on per-plugin basis, based on the version selected by the user. For example, the release 2.4 of the Javadoc Plugin already included MJAVADOC-165, breaking with its previous release 2.3 (btw, are there objections from users regarding this change?). So it's not about switching from Maven 2.0.x to Maven 2.1 but from Plugin x.y to x.y+1 which I feel is the same step.
I would like to see the results of a user list poll before we go much futher.
Alright, thanks for confirmation, I will then send a vote to [EMAIL PROTECTED] to get us a more founded impression of community desire. Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
