Community
Participate
Working Groups
in 3.6.x (0902-1717 build)... An error occurs when importing a plugin from disk. It appears that if there is a related source bundle then the problem happens. reproduce as follows 1) download the Eclipse project test harness zip and unzip at some place on your drive. This gives you, amongst other things, the org.eclipse.test and org.eclipse.test.source folders (both version 3.3.0) 2) in your workspace use Import > Plugin development > plugins and fragments. Indicate the location at which you unzip'd the test harness. click next. Ensure you are importing the plugins as BINARY projects (first option) 3) On the plugin page Add the org.eclipse.test plugin to the list ot be imported. Click OK/Finish. 4) notice the error below Problems detected while importing plug-ins /Users/jeff/Desktop/eclipse/plugins/org.eclipse.test.source_3.3.0 (No such file or directory) /Users/jeff/Desktop/eclipse/plugins/org.eclipse.test.source_3.3.0 (No such file or directory) If you look in the log you will see something like... !ENTRY org.eclipse.pde.ui 4 0 2010-09-07 15:50:50.194 !MESSAGE Problems detected while importing plug-ins !SUBENTRY 1 org.eclipse.pde.ui 4 0 2010-09-07 15:50:50.194 !MESSAGE /Users/jeff/Desktop/eclipse/plugins/org.eclipse.test.source_3.3.0 (No such file or directory) !STACK 0 java.io.FileNotFoundException: /Users/jeff/Desktop/eclipse/plugins/org.eclipse.test.source_3.3.0 (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:106) at org.eclipse.pde.internal.ui.wizards.imports.PluginImportHelper.copyArchive(PluginImportHelper.java:206) at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.importSourceArchives(PluginImportOperation.java:787) at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.importAsBinary(PluginImportOperation.java:380) at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.importPlugin(PluginImportOperation.java:342) at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.runInWorkspace(PluginImportOperation.java:147) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) 5) looking on disk, the desired location does in fact exist. There is a question as well as to why the import operation is looking at/for source bundles anyway since the workflow indicated BINARY projects not projects with source.
PDE looks up the source bundles for a binary import to get schema files and source for the binary plug-in. The source is not imported, but is attached to the plug-in container so source is available for debugging. No idea what is going on here if the file exists but Java.IO says it doesn't.
Makes sense (the looking for source bundles for schemas). As for not finding the location one thing I did notice is that the test.source plugin does not show up in the list of bundles to import. I assumed that that was some smart filtering on PDEs part. I did happen to get the test harness build from 3.5.1 and import the bundles as projects from that. When I went through that workflow the source bundle DID show up in the list and the import completed fine. Thoughts: - The more recent source bundles have the new funky source bundle layout (with automatedsrc dirs) and the have the Eclipse-BundleSource header whereas the old source bundles were just normal bundles with src dirs. - I happened to notice that the test.source bundle is a folder (not a jar) but that is true in both the new and 3.5.1 builds. (seems like a bug that that is so but its a different bug...)
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.
