Bug 3895 - Refactoring introduces errors due to wrong scope (1GF5H8C)
Summary: Refactoring introduces errors due to wrong scope (1GF5H8C)
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Windows NT
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Adam Kiezun CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 3339
Blocks:
  Show dependency tree
 
Reported: 2001-10-10 23:02 EDT by Dani Megert CLA
Modified: 2002-08-21 06:19 EDT (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 Dani Megert CLA 2001-10-10 23:02:38 EDT 
Because refactoring is applied to the whole workbench it also
	updates other projects which might not be related to the one
	I apply the refactoring. This can introduce errors into the
	workbench:

	1. Add JProject1 and import JUnit
	2. Add JProject2 and import JUnit
	3. (optional: add JProject1 to the classpath of JProject2)
	4. Rename the package junit.framework to _junit.framework
	==> package imports of JProject1 are also changed and
			result in compile errors since JProject2 is not visible (on CP)

AK (8/16/2001 7:03:21 PM)
	waiting for: 1GIJU1P: ITPJCORE:WINNT - search: java project scope does not work as expected

AK (10/9/2001 3:45:43 PM)
	fixed for 204 - case with projects that do not reference each other
Comment 1 Adam Kiezun CLA 2001-10-17 09:12:15 EDT 
waiting
Comment 2 DJ Houghton CLA 2001-10-24 07:24:02 EDT 
PRODUCT VERSION:
	0.122
Comment 3 Adam Kiezun CLA 2002-07-26 12:38:25 EDT 
probably dead already - reopen to verify
Comment 4 Adam Kiezun CLA 2002-08-21 06:19:59 EDT 
works now