Bug 3912 - no refactoring should be available on .java files from resource folders (1GF5UQM)
Summary: no refactoring should be available on .java files from resource folders (1GF5...
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P4 major (vote)
Target Milestone: ---   Edit
Assignee: Adam Kiezun CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 23:02 EDT by Erich Gamma CLA
Modified: 2001-11-12 05:12 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 Erich Gamma CLA 2001-10-10 23:02:55 EDT 
AK (6/11/01 4:35:16 PM)
	1. add a resource (not source) folder to your project
	2. create a java class in it (or, rather, drag and drop a compilation unit in there)
	3. observe: you cannot rename the compilation unit (i mean, it only renames the file then)
		which is correct - it just happens to ba a .java file but it is just a resource

	4. however, you can invoke all other refactorings - which is wrong

AK (6/11/01 4:39:54 PM)
	why is it a ICompilationUnit then?
	why opening it opens the java editor?
	why is the outliner populated?
	why ...
	it is just a resource file with .java extension
Comment 1 Martin Aeschlimann CLA 2001-10-16 11:13:56 EDT 
moved to 'active'
Comment 2 DJ Houghton CLA 2001-10-24 07:24:33 EDT 
PRODUCT VERSION:
	122
Comment 3 Erich Gamma CLA 2001-11-10 16:54:56 EST 
refactorings should only be enabled for java files on the build path.
otherwise refactorings don't makes sense since we only index Java files on the 
build path.
Comment 4 Adam Kiezun CLA 2001-11-12 05:12:56 EST 
not a problem now - i did nothing but .java files are in folders (out of 
classpath) are not reported as cus anymore (only as resources)

closing