Bug 247450

Summary:	Changing project encoding crashes compilation
Product:	[Eclipse Project] JDT	Reporter:	Blazej Kroll <blazej.kroll>
Component:	Core	Assignee:	Jerome Lanneluc <jerome_lanneluc>
Status:	VERIFIED NOT_ECLIPSE	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert, krzysztof.daniel, Olivier_Thomann
Version:	3.2.2
Target Milestone:	3.5 M3
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Blazej Kroll

2008-09-16 09:46:10 EDT

Build ID: 3.3

Steps To Reproduce:
1. Set the encoding of workspace to some cp* (e.g. cp1250)

2.Create a simple Java project with a string containing some national specific characters (e.g. ó é)

3. Change the workspace encoding to UTF-8 with Window -> Preferences -> General -> Workspace -> Text File Encoding

4. Error appears which reads: 
The project was not built since the source file TestUTF8/Test.java could not be read


More information:
When changing the encoding back to cp1250 the file is accessible again.

Comment 1 Dani Megert

2008-09-16 10:38:40 EDT

I cannot reproduce. Can you attach an example project? Which VM? Are you sure it was on Windows and not on Linux?

Comment 2 Blazej Kroll

2008-09-17 08:06:30 EDT

 I changed the Eclipse version which this bug is reported against. Sorry, must have mischecked it earlier.

  I can see it is working in 3.4 (the file opens and the problematic chars are replaced with boxes/squares but the file can be found by Eclipse compiler).

  Could not find any bug which has the patch covering this issue for 3.2.2, is there any or was it implemented as a new feature?

Comment 3 Jerome Lanneluc

2008-09-19 06:41:15 EDT

I cannot reproduce in 3.3.2. Or did you see it in a previous version?

Comment 4 Dani Megert

2008-09-19 06:56:21 EDT

>I cannot reproduce in 3.3.2. Or did you see it in a previous version?
It looks like he has the problem in 3.2.2.

Comment 5 Jerome Lanneluc

2008-09-19 07:18:46 EDT

(In reply to comment #4)
> >I cannot reproduce in 3.3.2. Or did you see it in a previous version?
> It looks like he has the problem in 3.2.2.
Oops, it looks like I misread the version field. Thanks Dani.

Comment 6 Jerome Lanneluc

2008-09-19 07:23:05 EDT

But I cannot reproduce with 3.2.2 either.

Comment 7 Krzysztof Daniel

2008-10-10 09:55:28 EDT

I have investigated this a little bit and it looks like this is VM problem.

sun.io.MalformedInputException is thrown when one tries to open specific files when using IBM J9. Sun VM works OK. 

I propose to close this bug as NOT_ECLIPSE.

Comment 8 Jerome Lanneluc

2008-10-10 10:43:15 EDT

Thanks for getting back to us.
Closing as NOT_ECLIPSE

Comment 9 Olivier Thomann

2008-10-27 16:36:11 EDT

Verified for 3.5M3 using I20081026-2000