Bug 38463 - Delete: Removing a project does not update requiring projects
Summary: Delete: Removing a project does not update requiring projects
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M6   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-05 05:36 EDT by Martin Aeschlimann CLA
Modified: 2003-12-09 07:58 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 Martin Aeschlimann CLA 2003-06-05 05:36:27 EDT 
20030604

1. create Java projects A and B, let A have B on its classpath
2. remove B.
3. A still contains B on the class path

I think the best solution would be when the confirmation dialog contains a
checkbox asking if all references in classpath should be removed as well.

Note that for source folders a remove also removes the classpath entry
Comment 1 DJ Houghton CLA 2003-06-05 13:40:02 EDT 
Updating the project reference is a duplicate of bug 2855.
Classpath is controlled by JDT/Core.
Moving for comment.
Comment 2 Philipe Mulet CLA 2003-12-09 07:58:11 EST 
We don't remove the project automatically as it may be triggered by a CVS 
action or a PDE import. If we did remove the prereq, then who is going to add 
it back during a replace operation ?

Same behavior when replacing package fragment roots, we do not touch the 
classpath on purpose.