Bug 310623 - core.runtime needs to implement Character.isHighSurrogate()
Summary: core.runtime needs to implement Character.isHighSurrogate()
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.6   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 307821
  Show dependency tree
 
Reported: 2010-04-27 08:55 EDT by Serge Beauchamp CLA
Modified: 2019-09-06 16:12 EDT (History)
4 users (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 Serge Beauchamp CLA 2010-04-27 08:55:33 EDT 
Because the platform is still using jdk 1.4, it doesn't have access to some APIs such as Character.isHighSurrogate().

This particular API is required to fix bug 307821.

Some common eclipse core plugin should make those missing APIs available to the eclipse platform plugins, so that they do not have to duplicate the implementation everywhere.
Comment 1 Paul Webster CLA 2010-04-27 09:24:01 EDT 
The functionality is available in com.ibm.icu.lang.UCharacter, but there's no matching replacement class in the ICU base.

At this time RCP and Platform aren't using anything from ICU that's not in the base ICU plugin to allow it to be swapped out for that standard JRE behaviour, and I don't think we want to change that.  See bug 309468, bug 234245

It maybe that we need to fix this in 3.7 by moving org.eclipse.core.resources to 1.5

PW
Comment 2 Szymon Brandys CLA 2010-04-27 09:46:26 EDT 
(In reply to comment #1)
> It maybe that we need to fix this in 3.7 by moving org.eclipse.core.resources
> to 1.5

Paul, do you know what the process is to do it? We could try to start it once 3.6 is released.
Comment 3 John Arthorne CLA 2010-04-27 12:22:13 EDT 
There isn't really any process for this, but I'm sure we'll want to have a discussion about it in the PMC first. Since the alternate fix requires new API anyway, we can defer this until 3.6 is out.
Comment 4 Mike Wilson CLA 2010-04-28 09:20:42 EDT 
Agree that we need to wait until post 3.6, but we can start the discussion now. Suggest we add this to the agenda for the next PMC call.
Comment 5 Szymon Brandys CLA 2010-04-29 10:43:50 EDT 
(In reply to comment #4)
> Agree that we need to wait until post 3.6, but we can start the discussion now.

I raised Bug 311012 to track the discussion about moving core.resources to 1.5.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:12:19 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.