Community
Participate
Working Groups
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.
I think that was already broken in previous releases.
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.
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.
works on Version: 2021-12 (4.22) Build id: I20210929-1800