Bug 44580 - No outline when unit name is not valid
Summary: No outline when unit name is not valid
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M5   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-09 12:44 EDT by Frederic Fusier CLA
Modified: 2003-11-19 10: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 Frederic Fusier CLA 2003-10-09 12:44:58 EDT 
I have a compilation unit "Example.java" in a java project.

In the Resource perspective, I rename this file "Example .java" which is 
obviously an invalid name for a java file, the outline goes away although I 
wouldn't expect any change in it.

If I rename the file "Example1.java" which is a valid one, then the outline 
comes back and got the expected error:
"The public type Example must be defined in its own file"
Comment 1 Frederic Fusier CLA 2003-10-09 12:46:27 EDT 
When I said "...Outline goes away..." this mean than it becomes empty not that 
this view was closed abruptely...
Comment 2 Philipe Mulet CLA 2003-10-10 17:55:40 EDT 
Fixed, this was a consequence of unnecessary validation of handles, see bug 
44662

*** This bug has been marked as a duplicate of 44662 ***
Comment 3 Philipe Mulet CLA 2003-10-10 18:21:10 EDT 
Actually, there was more to it. Commit did not work always (see 
WorkingCopyNotInClasspathTests#testReconcileAndCommit4,
WorkingCopyNotInClasspathTests#testReconcileAndCommit5)
Comment 4 Philipe Mulet CLA 2003-10-10 18:22:04 EDT 
Fixed (commit working copy operation)
Comment 5 David Audel CLA 2003-11-19 10:12:47 EST 
Verified.