Set project encoding to UTF-8

[fedejeanne]

It was done using a "Quick Fix" and the value set (UTF-8) is the same value that any other project in the workspace uses. The objective of this commit is to declutter the "Problems" view.

[iloveeclipse]

You are adding settings to something that is not even a project!

[fedejeanne]

You are adding settings to something that is not even a project!

Technically, it is a project:

It's the parent maven project, a "POM" project.

Do you think the logic in the ValidateProjectEncoding (see this comment) should be changed?

[iloveeclipse]

It's the parent maven project, a "POM" project.

Sure, but not an Eclipse project.

Do you think the logic in the ValidateProjectEncoding (see this comment) should be changed?

No, I think the logic is fine. You should simply not import this folder as an Eclipse project.

[fedejeanne]

It's the parent maven project, a "POM" project.

Sure, but not an Eclipse project.

I see, I will withdraw this PR. I still think that if this is the criteria then the ValidateProjectEncoding should at least check the nature of the project and exclude the "pure Maven" projects with a POM-packaging, don't you think?

Do you think the logic in the ValidateProjectEncoding (see this comment) should be changed?

No, I think the logic is fine. You should simply not import this folder as an Eclipse project.

I didn't import them myself, I used the installer (see comment). I hope Ed can fix the issue to prevent this in the future :-)

[iloveeclipse]

You didn't get it. This is not a project because in git, there is no ".project" file.
And once again, ValidateProjectEncoding logic is fine. The problem is that you seem to imported lot of folders as projects. Once you do that, locally you personally have projects, where in reality there shouldn't be a project at all.

[fedejeanne]

👍

The problem is that you seem to imported lot of folders as projects.

Odd, I wasn't even aware that was possible. Thank you for the clarification!