Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 437185

Summary:	Unable to import exploded source bundle
Product:	[Eclipse Project] PDE	Reporter:	Brian de Alwis <bsd>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	curtis.windatt.public
Version:	4.4	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X
Whiteboard:	stalebug

Description Brian de Alwis

2014-06-11 10:34:56 EDT

I added Jetty to a target platform and wanted to import a plugin as source which failed as the source bundle was a directory rather than a jar (jetty's source feature org.eclipse.jetty.bundles.f.source has org.eclipse.jetty.osgi.boot.source plugin set to be unpacked).

java.io.FileNotFoundException: /Users/bsd/Manumitting/Projects/NearHere/workspace/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.eclipse.jetty.osgi.boot.source_8.1.15.v20140411 (Is a directory)
	at java.util.zip.ZipFile.open(Native Method)
	at java.util.zip.ZipFile.<init>(ZipFile.java:220)
	at java.util.zip.ZipFile.<init>(ZipFile.java:150)
	at java.util.zip.ZipFile.<init>(ZipFile.java:164)
	at org.eclipse.pde.internal.ui.wizards.imports.PluginImportHelper.extractJavaSourceFromArchive(PluginImportHelper.java:143)
	at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.extractSourceFolders(PluginImportOperation.java:927)
	at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.importAsSource(PluginImportOperation.java:563)
	at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.importPlugin(PluginImportOperation.java:452)
	at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.runInWorkspace(PluginImportOperation.java:246)
	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Comment 1 Eclipse Genie

2019-10-11 01:52:43 EDT

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.

--
The automated Eclipse Genie.