Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 512490

Summary: JDT compiler chokes on non-ASCII during export
Product: [Eclipse Project] JDT Reporter: Christian Sell <c.sell>
Component: CoreAssignee: JDT-Core-Inbox <jdt-core-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: jarthana, Vikas.Chandra
Version: 4.6   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug

Description Christian Sell CLA 2017-02-21 06:40:22 EST 
when performing a "delayable plugin" export from the PDE, an error is raised and the log shows this:

53. ERROR in C:\work\klarios\workspace\klarios-ng\com.atissystems.aal\src\com\atissystems\aal\access\IOHandlerDB.java (at line 960)
	protected final static DBKey getDBKey(@Nonnull final Config config, @Nonnull final String key, @Nullable final DBKey défault) throws ConfigError, InvalidName
	                                                                                                                       ^^^^^^
Syntax error on tokens, delete these tokens
----------
54. ERROR in C:\work\klarios\workspace\klarios-ng\com.atissystems.aal\src\com\atissystems\aal\access\IOHandlerDB.java (at line 966)
	else if (défault != null)

the actual code reads "défault" for the words in question (french accent on the e to avoid keyword conflict), which is legal java nowadays
Comment 1 Eclipse Genie CLA 2019-09-10 18:45:57 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Jay Arthanareeswaran CLA 2019-09-11 02:55:35 EDT 
This never got our attention and sorry about it.

Christian, is this a UTF character?
If so, can you confirm that your project is at a Java level that supports this particular UTF version?