Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-pmc] Approval needed for moving org.eclipse.core.resources plug-in to Java 1.5

I am also, +1, with the caveat that, although it makes perfect sense to *use* the capabilities of 1.5, we need to be careful when we talk about "modernizing" the API. New API is fine, but it can't be done at the cost of the existing API, which we still have to support for the foreseeable future.

McQ.

Inactive hide details for John Arthorne---2010/11/08 17:31:11---+1 from me. Although there is no single killer reason for this,John Arthorne---2010/11/08 17:31:11---+1 from me. Although there is no single killer reason for this, every year there are one or two smaller issues that crop up tha


From:

John Arthorne/Ottawa/IBM@IBMCA

To:

eclipse-pmc@xxxxxxxxxxx

Date:

2010/11/08 17:31

Subject:

Re: [eclipse-pmc] Approval needed for moving org.eclipse.core.resources plug-in to Java 1.5





+1 from me. Although there is no single killer reason for this, every year there are one or two smaller issues that crop up that require us to roll our own implementation of something that would be available in Java 5 if we could use it. I think we're at the point where this accumulation of issues outweighs the risk that there may still exist someone wanting to use the resource model in more constrianted environments (and we're not aware of any such consumers still existing in 3.7 stream).




Szymon Brandys <Szymon.Brandys@xxxxxxxxxx>
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx

11/08/2010 12:38 PM

Please respond to
eclipse-pmc@xxxxxxxxxxx
To
eclipse-pmc@xxxxxxxxxxx
cc
Subject
[eclipse-pmc] Approval needed for moving org.eclipse.core.resources plug-in to Java 1.5




This is a request to approve moving core.resources to Java 1.5. The
benefits are:
- making use of i18n libraries that aren't available elsewhere (e.g., high
surrogate support) to fix bugs like
https://bugs.eclipse.org/bugs/show_bug.cgi?id=310623
- modernizing our API and using generics, varargs, enums, etc, where
appropriate
- moving to Java 5 data structures that we previous had to maintain copies
of: Queue, CopyOnWriteList, etc.

Corresponding bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=311012

--
Szymon Brandys

_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc
_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc


GIF image

GIF image


Back to the top