Bug 5493 - Adding project references doesn't update the classpath
Summary: Adding project references doesn't update the classpath
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-02 14:57 EST by John Arthorne CLA
Modified: 2002-01-11 09:22 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Arthorne CLA 2001-11-02 14:57:25 EST 
When a project is added to the source path for a java project, it automatically 
adds a core project reference.  The reverse is not true, adding a project 
reference does not automatically update the source path.  Consider doing this to 
ensure consistency between the two lists...
Comment 1 Philipe Mulet CLA 2001-11-02 16:49:51 EST 
Project references are used by the Java tooling to induce a build order 
consistent with the classpath settings.

In case a project had more than the Java nature, other tooling might set 
further project references to control further the build order. These references 
would however not be meaningfull for a Java classpath.

So I do not think it would make sense to do it this way. But I understand that
it would though be practical to directly set project references in the UI and 
have them be ordered on the classpath afterwards.