Description Luke Evans 2003-10-16 17:19:02 EDT

We have many occasions where the basic (project) classpath needs to be customised by individuals 
when actually running or debugging the app.  Such a requirement is surely not unusual where apps 
perform dynamic classloading (i.e. for plugins/discovered functionality).  Although Eclipse currently 
provides a way to specialise the classpath in run configurations (away from the project settings), 
this is at the expense of 'disconnecting' the classpath from inevitable changes in the 'build 
classpath', which is frequently the cause of problems.  

It would be very nice to be able to configure run settings to always include whatever the build 
configuration specifies in terms of classpath, and ADD some classpath settings (projects, JARs etc.) 
that are specific to the particular run configuration.