[news.eclipse.platform] Source locations in target platform use absolute

[Petra Kritzinger <petra.k@xxxxxxxxxxx>]

Hi!

We are developing Eclipse plugins in a multi-user environment using CVS.
The problem is that Eclipse hard-codes absolute paths in the java build
path.

A work-around is to add the jars that a project uses (both eclipse and 3rd
party jars) in a new project/jar-folder (booked into CVS), declare a
classpath variable pointing to the local workspace, and include all the
jar files from the relevant application. All users should then declare the
same classpath variable, pointing to their own workspace.

My question is the following: when creating a new plugin project, the
build path is automatically filled. I found the source for this in window
> preferences > plugin development > target platform > source code
locations - is there a way to change these to rather use the classpath
variable, ECLIPSE_HOME?

The same applies for creating a java application and then adding the SWT
(and/or jface) library through project properties > java build path >
libraries > add library > swt.

Thanks!