Community
Participate
Working Groups
- older workspace - today's build (June17) I have a non-Java project that is getting a .classpath generated. If I delete the .classpath, or replace the project with the content from the repo, the .classpath is regenerated (as confirmed by checking date on the file). I am not sure how I've gotten into this state. The project in question is the isv project (org.eclipse.platform.doc.isv). I've checked the .project and there is no java nature or builder. I had both it and the user doc already in my workspace and both were exhibiting this same .classpath generation behaviour. Deleting the user doc project and reloading it from the repo yielded a correctly working non-java project. I also tried just creating a new simple project but didn't get the .classpath behaviour. So I'm not sure how you are going to reproduce this. The .classpath looks like: <?xml version="1.0" encoding="UTF-8"?> <classpath> <classpathentry kind="src" path=""/> <classpathentry kind="output" path="bin"/> </classpath> Note that these directories don't exist in the project in question, suggesting that this .classpath is being generated from a different project. I have several java source and non-source projects in my workspace. I've taken the new build but have not yet re-imported the plugins. Can't think of any other relevant details. I have the workspace zipped and will provide if needed.
Note this project *does* have a plugin.xml (perhaps related, perhaps not). With PDE decorators turned on, its _not_ marked as a PDE project.
Just to clear any confusion, PDE does not mark PDE projects specifically - decorators are used only for binary projects (those created by importing them using the Import External Plug-ins wizard). A PDE project is a project with a manifest (plugin.xml, fragment.xml) that has both Java and PDE perspective. PDE does not require PDE perspective in order to correctly operate, though (you will not get builders that are registered for a nature and some nature-specific actions).
This is easily reproducable by following these steps: 1. Start Eclipse on a new workspace 2. Import the two doc plugins (org.eclipse.platform.dic.isv and org.eclipse.platform.doc.user) as binary plugins. 3. Checkout the above projects from dev.eclipse.org. 4. .classpath files are created
*** This bug has been marked as a duplicate of 16140 ***
reopening
moving to PDE
Note that .classpath is present after step 2.
Fixed. New code has been released in HEAD.
Re-opening. The fix introduced a regression bug. The problem is that upon importing plug-ins as binary projects, there is really NO way of knowing if they are Java projects or not. So the assumption that we make is that they all are Java projects, which is correct "most of the time".
Kevin, The plugin project org.elcipse.platform.doc.isv does contain a library entry (activeHelpSample.jar), which contains one Java class. So the project should be marked as a Java project and its classpath should be computed. As for the org.eclipse.platform.doc.user, it does not contain a library entry. So it should not have a java nature or its classpath computed. This is a bug that I fixed and will be in 2.1
