[eclipse-dev] Deprecations in Runtime

[Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>]

I have released a set of deprecations
to API in org.eclipse.core.runtime.  These deprecations highlight
areas where function in the runtime proper in fact depends on the presence
of the runtime compatibility layer.  This represents a major step
for people who are trying to move onto the new API.  Previously they
had to laboriously (and manually) scan their code for references to types
and methods which were marked as "obsolete" using plain text
in the javadoc.  Now the obsolete code is marked with real deprecations
and developers can use the compiler warnings to find their references.

****** The deprecation of this code
does NOT affect its validity or correctness for use in Eclipse 3.0.  ******

You can continue to use and rely on
them and their specifications have not otherwise changed.  Unless
you have functional need to get off of the compatibility layer, no particular
action is required.

Note to the Eclipse teams:  We
are shooting to have all of the plugins listed in as RCP base or optional
off the compatibility layer for 3.0.  Most have declared they are
already free of references.  As a case in point of why these deprecations
are valuable however, about 8 of those plugins were found to still require
compatibility when the deprecations were turned on.  I will work with
those teams to ensure that they are in fact free of ties to the compatibility
layer.

Jeff