[eclipse-dev] (no subject)

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

Plug-in developers in the 3.0 stream
will have noticed that changing self hosting styles (between external projects
and binary or source projects), causes outgoing changes to the .project
files of downstream plugins in your workspace. This is a consequence of
the switch in PDE to using dynamic classpath variables when updating plugin
classpaths. To make a long story short, it was necessary to update project
references in the .project file to ensure the workspace build order reflected
any changes to project classpaths.

As of today's integration build (I20040322),
and in 3.0 M8, project references computed via dynamic classpath variable
are no longer treated as "hard" project references and are no
longer stored in the .project file. The net result is that you should see
no further changes to your .project files when you change self-hosting
styles, or when you add and remove prerequisite plug-ins when self-hosting.
In fact, you can now remove all project references from your plug-in projects
if self-hosting in 3.0 M8 or greater. Keep in mind that older builds of
Eclipse will still require correct project references in order to compute
the workspace build order.  You should only remove project references
from your projects if everyone on your team is self-hosting with 3.0 M8
or greater. 

To summarize, NO ACTION IS REQUIRED
by you.  If everyone on your team is self-hosting on 3.0 M8 or greater
you can feel free to remove all project references from your plugin projects,
as they are no longer needed. If you want to get rid of any outgoing changes
on .project files in your workspace right now, you can safely select them
in the synchronize view and do an "Override and Update".

For all the gory details, see:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=46668