Community
Participate
Working Groups
Scenario to reproduce: 1) Start PDE Project wizard and enter 'com.example.xyz' for the project name. 2) Go to the end of the wizard by accepting the default values and selecting the default plug-in content wizard (the only choice in the provided list). Press Finish. 3) As a result, a project structure will be created and manifest editor will be opened. 4) Try to select the plug-in class hyperlink in the first page (top-left). It will not work. The reason it doesn't is because Java plugin cannot find the type. If you check the Packages view, there are no packages under 'src' folder even though it compiles nicely and 'bin' folder contains the class. The file exists in the Navigator and contains the correct package name. However, if I switch to the Navigator, close and then open the project again, the Java file is recognized and the hyperlink will open the file into the Java editor. This is a regression - it used to work in 1.0., but I don't know when this started to show up.
The fact that closing and reopening the project fixes the problem indicates a problem in the Java element info caching. Moving to Java Core
Some additional info: if the package is already present, creating new Java files by PDE under the same package seems to work. It looks like the problem shows up when the source folder does not contain a package and the generated Java file is the first in that package.
*** Bug 7306 has been marked as a duplicate of this bug. ***
Refresh problem
Could not reproduce in 20020205 (you didn't provide the build number btw). I'm getting the correct delta (i.e. the package is added), and there is a package under the src folder. Please re-open if you still see the problem.
regarding the bug 7306 duped into this one: I did provide the build number, and was not convinced that Dejan's bug was the same as this one; if I see it again, I'll try to get a better description and reopen 7306.
