Paolo Compieta wrote:
- most companies have uniform OS platforms
I am used to scenarios where people work on Unix/Win terminals or their
Unix/Mac/Win notebooks on their own discretion, creating quite some
heterogenous development culture. Might be one reason why I quickly had
locked down all encoding settings in our corporate POM...
- most editors allow you select a proper charset, but they (usually)
automatically detect the default ("file.encoding"); it'd be not
comfortable
changing every time the charset to a different one only because maven said
"this is the standard"; i.e., i wouldn't exchange platform-dependence with
implicit charset-dependence (potential drawbacks on all other kinds of
editor - java/sql/xml/properties/..)
If the proposed default value matches your platform encoding, you're just
fine. If it doesn't, you would simply configure your POM accordingly (i.e.
configure Maven for your needs and not vice-versa) and both you and in
particular all your co-workers are fine for the rest of their life, too. You
don't promote to edit the same file with different encodings selected for
your editor, don't you?
- big trans-national companies (should!) have centralized and
well-configured building-machine to be asked for deliverables;
Wouldn't you want to be able to create the same build output on your own dev
machine than the output from these "centralized and well-configured
building-machine"? For that reason, the encoding should be bound to the POM
(which is shared among all participants) in contrast to OS or locale.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
