Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug 516583 - Use UTF-8 as default encoding for *new* workspaces #51

Merged
merged 1 commit into from
Apr 15, 2022

Conversation

iloveeclipse
Copy link
Member

Set UTF-8 foor new workspace as default workspace encoding if Eclipse is
started without explicit encoding set (either as JVM system property
-Dfile.encoding=XYZ or by product customization preference
org.eclipse.core.resources/encoding=XYZ).

After that all projects created in this workspace will get explicit
UTF-8 encoding set (they will derive that from the workspace encoding
and not from some random encoding taken from current OS settings).

Existing workspaces or projects with explicit encoding set will be not
affected by the change.

This PR requires eclipse-platform/eclipse.platform.runtime#22 merged first

Set UTF-8 foor new workspace as default workspace encoding if Eclipse is
started without explicit encoding set (either as JVM system property
-Dfile.encoding=XYZ or by product customization preference
org.eclipse.core.resources/encoding=XYZ).

After that all projects created in this workspace will get explicit
UTF-8 encoding set (they will derive that from the workspace encoding
and not from some random encoding taken from current OS settings).

Existing workspaces or projects with explicit encoding set will be not
affected by the change.
@eclipse-releng-bot
Copy link
Contributor

The Jenkins build of this PR has now completed. See details at https://ci.eclipse.org/platform/job/eclipse.platform.resources/job/PR-51/4/

@iloveeclipse iloveeclipse marked this pull request as ready for review April 15, 2022 18:28
@iloveeclipse iloveeclipse merged commit 2fd2f4e into eclipse-platform:master Apr 15, 2022
@iloveeclipse iloveeclipse deleted the Bug_516583 branch April 15, 2022 18:31
iloveeclipse added a commit to iloveeclipse/eclipse.jdt.core that referenced this pull request Feb 19, 2023
Original test assumed workspace always uses system default encoding and
projects follow that if nothing is set explikcitly.

This assumption was not correct anymore after
eclipse-platform/eclipse.platform.resources#51
and eclipse-platform/eclipse.platform.resources@961d080

For the concrete test to succeed we should set "system" encoding on the
project we use.

Fixes eclipse-jdt#462
iloveeclipse added a commit to eclipse-jdt/eclipse.jdt.core that referenced this pull request Feb 19, 2023
Original test assumed workspace always uses system default encoding and
projects follow that if nothing is set explikcitly.

This assumption was not correct anymore after
eclipse-platform/eclipse.platform.resources#51
and eclipse-platform/eclipse.platform.resources@961d080

For the concrete test to succeed we should set "system" encoding on the
project we use.

Fixes #462
vogella added a commit to vogellacompany/eclipse.platform that referenced this pull request Jul 3, 2024
eclipse-platform/eclipse.platform.resources#51
implemented logic to set UTF-8 as standard.
I suggest to also set the default preference value to UTF-8.
robstryker pushed a commit to robstryker/eclipse.jdt.core that referenced this pull request Jul 18, 2024
Original test assumed workspace always uses system default encoding and
projects follow that if nothing is set explikcitly.

This assumption was not correct anymore after
eclipse-platform/eclipse.platform.resources#51
and eclipse-platform/eclipse.platform.resources@961d080

For the concrete test to succeed we should set "system" encoding on the
project we use.

Fixes eclipse-jdt#462
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants