Summary: | Invalid warning saying that a class is not in the bundle's classpath | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] PDE | Reporter: | Marcelo Paternostro <marcelop> | ||||||||
Component: | UI | Assignee: | Chris Aniszczyk <caniszczyk> | ||||||||
Status: | RESOLVED FIXED | QA Contact: | |||||||||
Severity: | normal | ||||||||||
Priority: | P3 | CC: | caniszczyk, Ed.Merks | ||||||||
Version: | 3.4 | Keywords: | contributed | ||||||||
Target Milestone: | 3.4 RC1 | ||||||||||
Hardware: | PC | ||||||||||
OS: | Windows XP | ||||||||||
Whiteboard: | |||||||||||
Attachments: |
|
Description
Marcelo Paternostro
2008-05-06 14:00:54 EDT
I guess that's fair, but how you actually created a Plug-in project w/ src and w/o the JDT nature, that surprises me. The magic of manipulating the .project file directly :-P Created attachment 99041 [details]
Check for a Java nature before looking for the classpath
Created attachment 99042 [details]
Here's a simpler way to fix it, i.e., check if the Java project is open
Playing with the .project file manually will get you into trouble. Also, I'm pretty good with the change, however, note that as soon as a project actually has java source code, it should be a java project. done.
> 20080507
Created attachment 99075 [details]
mylyn/context/zip
|