Summary: | parsing of classesd if more than one class in one file | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Klaus Dicks <kd> | ||||
Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> | ||||
Status: | RESOLVED WORKSFORME | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | ||||||
Version: | 3.2 | ||||||
Target Milestone: | 3.2 M6 | ||||||
Hardware: | PC | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Klaus Dicks
2006-03-23 07:08:45 EST
What is your build ID? (Help->About Eclipse SDK) Eclipse SDK Version: 3.2.0 Build id: I20060223-1656 Thanks, that's 3.2 M5a, so secondary types should work. Can you attach the class file to this bug? How did you get it in your workspace: import, copy/paste, other? Created attachment 36869 [details]
File with parsing errors
I've checked out the file via cvs to my workspace I can't reproduce your problem. Using a simpler test case: Test.java public class Test {} class Secondary {} Here's my scenario: 1) Create Test class in a workspace (say wksp1) 2) Release this new class in CVS repository 3) In another workspace (say wksp2), I replace my project with HEAD content 4) Open Type Dialog and type "Secondary" => I correctly see the new secondary type "Secondary" on top of proposed classes I got same correct result if at step 3) I do a syncronization + update or a check-out from repository in a third workspace where my project didn't exist. I've done this test with last integration build I20060322-1335 and also 3.2 M5, same correct result. Did I miss something? This morning I installed build I20060322-1335 and created my projects new and the error doesn't occur any more. I think it's solved. Fixed would imply that we have changed something in the code for this issue... => reopen to change resolution As I didn't succeed to reproduce in 3.2 M5, I would prefer to say that it simply works for me (and for you now)... |