Bug 582907 - Plugin-export of 'Deployable plug-ins and fragments' does not handle encoding correctly
Summary: Plugin-export of 'Deployable plug-ins and fragments' does not handle encoding...
Status: NEW
Alias: None
Product: Incubator
Classification: Eclipse Project
Component: e4 (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: E4 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-05 08:52 EST by kurt ablinger CLA
Modified: 2024-02-05 08:52 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description kurt ablinger CLA 2024-02-05 08:52:23 EST 
Depending on the java-version, 17 or 21, used to start Eclipse (SDK), the
output of the .class-binary is different for the same project.
The difference is NOT in program-byte-code, but in the strings containing
special characters like umlauts.

I also checked the .class-files in the bin-folder - these are compiled equally
in Eclipse started with java 17 oder 21.

A way to check the problem, is to have a plugin with a preferencepage which
sourcecode has umlauts in string-constants for the labels.
The sourcecode, the projects and the workspace encoding should be set to
CP1252.

To start eclipse with different java-versions I use a command like this:

  eclipse.exe -vm C:\Programs\open_jdk17\bin\server\jvm.dll
  eclipse.exe -vm C:\Programs\open_jdk21\bin\server\jvm.dll