Bug 337599

Summary:	Binary plug-in import doesn't work when plug-in is already in host workspace as source
Product:	[Eclipse Project] PDE	Reporter:	Markus Keller <markus.kell.r>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	curtis.windatt.public, daniel_megert, Vikas.Chandra
Version:	3.7	Keywords:	investigate
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Markus Keller

2011-02-18 13:52:51 EST

I20110215-0800

Binary plug-in import doesn't work when plug-in is already in host workspace as source. The plug-in Jar is not added to the build path.

Steps:
- new host workspace
- import org.eclipse.core.resources from CVS
- launch runtime workbench
- Import > Plug-ins and Fragments:
  - Import From: Directory
  - Import As: Binary projects
  - Next, import org.eclipse.core.resources

Bug: org.eclipse.core.resources_3.7.100.v20110207.jar is not on the build path.

Comment 1 Dani Megert

2011-02-21 09:17:50 EST

I think that was already broken in previous releases.

Comment 2 Curtis Windatt

2011-02-22 15:37:18 EST

This would be expected behaviour for importing from the target platform.  Because of target weaving, we would just copy the project from the host workspace into the runtime workspace.  However, when choosing to import from a directory (even a different directory than the current target), we are still copying from the host workspace.

There is probably a flaw in our logic where we check if target weaving applies.

Comment 3 Eclipse Genie

2019-08-13 14:15: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.

Comment 4 Eclipse Genie

2021-08-04 03:48:19 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.

Comment 5 Vikas Chandra

2021-10-18 01:51:56 EDT

works on
Version: 2021-12 (4.22)
Build id: I20210929-1800