[news.eclipse.platform] Re: Source locations in target platform use abso

[Ed Merks <merks@xxxxxxxxxx>]

Petra,

One way to avoid this is to use plugin projects exclusively, even if you ultimately don't need plugins because in that case there will be no direct references to any jars and the build results of a jarred plugin will work fine as just something you put on the classpath.  When developing plugins, you should NEVER modify the build path directly.  You should only edit the MANIFEST.MF and add dependencies via the Dependencies tab.  Any external jars you have should be put into their own plugin(s) and then other plugins that need these libraries will get them via plugin dependencies.


Petra Kritzinger wrote:

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!