Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Equinox Framework and several bundles moving up to Java SE 5 in Kepler

Much of the platform has now moved to Java 5, so there is certainly no longer any barrier to using generics in the API. I don't expect a major investment in revisiting all the old APIs to generify them at this point though. If there are particular examples that you think are high value I suggest entering a bug for it. Our early APIs made heavy use of arrays rather than untyped collections, so there might be less value than you think. I revisited a few classes in the past with an eye to adding generics and there were very few places where it was needed.


Alex Blewitt <alex.blewitt@xxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

10/05/2012 08:17 PM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
eclipse-dev@xxxxxxxxxxx, Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Re: [equinox-dev] Equinox Framework and several bundles moving up        to Java SE 5 in Kepler

With the upgrade to Java 5 for Kepler, are we likely to see the use of generics across the platform increase, for example, for getting services and selections?


On 5 Oct 2012, at 23:39, Thomas Watson wrote:

The following bundles (and framework) are moving up to Java SE 5 in Kepler M3:

 org.eclipse.osgi (the framework)

The framework and these equinox bundles have long supported J2ME Foundation VMs.  The OSGi R4.3 specification introduced generics to the API but we still continued to support J2ME by using the jsr14 compiler flag to compile the source into a binary that could still run on J2SE 1.4 based VMs (including J2ME).  With Java 7 the compiler (javac not the eclipse compiler) no longer supports class files compiled with the jsr14 option see [1] for more details.  J2SE 1.4 has long been considered end of life and our ability to support J2ME over the years has become more and more difficult.  Instead of continuing to try and use the jsr14 flag we have decided to simply move up to Java SE 5.  If Java 8 ends up including compact profiles [2] then we will of coarse look to supporting the smallest profile possible.



equinox-dev mailing list

equinox-dev mailing list

Back to the top