[MNG-7763] Provide UTF-8 as a default value for project.build.sourceEncoding and project.reporting.outputEncoding

[gnodet]

JIRA issue: https://issues.apache.org/jira/browse/MNG-7763
Discussion: https://lists.apache.org/thread/0mjosk1wp58fjvhz812htqfjot0n930g

[michael-o]

The outcome is then there is no way to remove this and it will also apply to ALL projects.

[gnodet]

The outcome is then there is no way to remove this and it will also apply to ALL projects.

Isn't that the goal ?
Also you can't remove the property, but you can override it, which is very often the case (else you actually have a warning).

[michael-o]

The outcome is then there is no way to remove this and it will also apply to ALL projects.

Isn't that the goal ? Also you can't remove the property, but you can override it, which is very often the case (else you actually have a warning).

Maybe, but this should be known that due to Plexus we cannot null values. @kwin Can we know? I don't that this is a huge problem here, but people should still know whether it is possible or not. I haven't used anything else, but UTF-8 for the past 20 years.

[rmannibucau]

while you can override it in your own project (which is the case AFAIK) it is fine and I don't see how null and not be deterministic can be better than forcing the value to the OS one so guess we are good like that without handling null in the code.

[kwin]

FTR: overwriting default values by empty string is not supported due to https://github.com/eclipse/sisu.plexus/issues/29

[ge0ffrey]

For those that want to override it to the Maven 3 behaviour, maybe you can introduce a magic value "OS_DEFAULT" that gets translated to not setting the encoding deeper down the implementation?

+1 to default to UTF-8

[michael-o]

For those that want to override it to the Maven 3 behaviour, maybe you can introduce a magic value "OS_DEFAULT" that gets translated to not setting the encoding deeper down the implementation?

+1 to default to UTF-8

I'd prefer system. This is what I have done in other Maven components where empty was not allowed.

[ge0ffrey]

Good point.

[ge0ffrey]

For what's it worth, I ran an online poll around this topic a few days ago:

I might have biased it a bit in how I posed the question :)

[gnodet]

For those that want to override it to the Maven 3 behaviour, maybe you can introduce a magic value "OS_DEFAULT" that gets translated to not setting the encoding deeper down the implementation?
+1 to default to UTF-8

I'd prefer system. This is what I have done in other Maven components where empty was not allowed.

I'd suggest that people that want the default encoding use ${file.encoding} so that we don't have to do any hack in maven.

[michael-o]

For those that want to override it to the Maven 3 behaviour, maybe you can introduce a magic value "OS_DEFAULT" that gets translated to not setting the encoding deeper down the implementation?
+1 to default to UTF-8

I'd prefer system. This is what I have done in other Maven components where empty was not allowed.

I'd suggest that people that want the default encoding use ${file.encoding} so that we don't have to do any hack in maven.

You are totally right. Stupid me.

[michael-o]

With the correction from @gnodet , I am fine with that. We need to properly document what is the scope of impact: Reactor or deps as well.