Bug 294005 - [import] Importing in target fails because plug-in models only have 'bin' as libraries (target weaving)
Summary: [import] Importing in target fails because plug-in models only have 'bin' as ...
Status: RESOLVED WORKSFORME
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: readme
Depends on:
Blocks: 294008
  Show dependency tree
 
Reported: 2009-11-02 17:52 EST by Curtis Windatt CLA
Modified: 2019-09-02 15:12 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Curtis Windatt CLA 2009-11-02 17:52:57 EST
1) Open the import plug-in wizard
2) Choose to import from a directory, point to an Eclipse install
3) Import org.eclipse.pde.core as binary

The imported plug-in is has no referenced libraries.  This is because instead of getting the correct libraries from the model [".","ant_tasks/pde-ant.jar"] we get ["bin/"].

This applies to all the import modes (binary/link/source), but the import works correctly when importing from a target (active or otherwise).
Comment 1 Curtis Windatt CLA 2009-11-02 17:53:39 EST
Needs investigation in 3.6.  Not a major problem because it only affects importing from directories.
Comment 2 Curtis Windatt CLA 2009-11-03 14:33:44 EST
This bug can be encountered anytime a PDEState is created when running in a target (development mode).  Anytime development mode is on, target weaving tries to update manifest headers based on what is in the dev.properties file.

The target weaver only has a map of plugin ID to classpath (from dev.properties) and a bundle location.  It does not have a target for context or any other info to determine whether it should weave or not.

In this case, during the import we are creating a PDEState.  We could pass in some sort of flag to tell the state not to weave the target.  However, this would require significant changes to how we create the state.  For now I'm just going to make a note in the import code.
Comment 3 Eclipse Genie CLA 2019-02-23 20:31:08 EST
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 Lars Vogel CLA 2019-09-02 15:11:23 EDT
This bug has been marked as stalebug a while ago without any further interaction.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.
Comment 5 Lars Vogel CLA 2019-09-02 15:12:18 EDT
This bug was marked as stalebug a while ago. Marking as worksforme.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.