Community
Participate
Working Groups
When a project doesn't have a JDT nature, PDE cannot compute the project's classpath and, hence, cannot check if a class used in the plugin.xml is available to the bundle or not. I believe PDE should only flag classpath problems if it is able to check the classpath. The way it is now, thw warning is not doing me any good and I would need to add the JDT nature just to make it go away.
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
