Bug 255802

Summary:	compile error in R3_0_maintenance branch of org.eclipse.wst.jsdt.ui
Product:	[WebTools] JSDT	Reporter:	David Williams <david_williams>
Component:	General	Assignee:	Phil Berkland <berkland>
Status:	RESOLVED FIXED	QA Contact:	Phil Berkland <berkland>
Severity:	normal
Priority:	P1	CC:	thatnitind
Version:	3.1
Target Milestone:	3.0.4
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description David Williams

2008-11-19 09:49:11 EST

in my R3_0_maintenance dev env there is a compile error in 
org.eclipse.wst.jsdt.ui

The method isWhitespace(char) in the type Character is not applicable for the arguments (int)   
FastJavaPartitionScanner.java   
org.eclipse.wst.jsdt.ui/src/org/eclipse/wst/jsdt/internal/ui/text       
line 108        
Java Problem


The odd thing is the code that has 'isWhitespace(char)' is not released, and is not in the HEAD version of this bundle. 

VERY confusing. Code that has been committed should normally be "ready to be released" at any time. 

Obviously, this code isn't ready to be released, so thought I'd open this bug.

Comment 1 David Williams

2008-11-19 09:52:48 EST

I'm marking as "P1" since this shouldn't be fixed quickly, before anyone forgets what it is about. 

Should something be reverted? Or should the manifest be changed to specify a BREE 1.5 and then the change propagated to HEAD? (BTW, normally you wouldn't want to change the BREE is a maintenance release, unless there's no alternative ... it is basically an API change).

Comment 2 Nitin Dahyabhai

2008-11-20 13:36:11 EST

Just a glitch with the Execution Environment setup, I think.  The form of isWhitespace(int) is present in 1.5 and higher while isWhitespace(char) is in 1.1 and higher.

Comment 3 Phil Berkland

2008-11-21 16:35:54 EST

Checked in fix (to cast to char).

Comment 4 David Williams

2008-11-22 03:32:56 EST

I still see the exact same error in the R3_0_maintenance branch. Could you have checked something in to head?

Comment 5 Nitin Dahyabhai

2008-11-24 12:01:50 EST

You're certain everything's set up correctly in your environment, David?  I'm *not* seeing the error any more.

Comment 6 David Williams

2008-11-24 13:58:40 EST

Yeah, it looks fine now ... I think cvs was broken so I was not synching up like I thought I was. 

Thanks,