Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 328349 - Required plug-ins evaluation in launch config has version problems
Summary: Required plug-ins evaluation in launch config has version problems
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-21 09:38 EDT by Alain Picard CLA
Modified: 2019-09-09 02:30 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alain Picard CLA 2010-10-21 09:38:10 EDT
Build Identifier: 20100617-1415

When using the "Add required plug-ins" button in the Plug-ins tab of the launch configuration, the added plugins are missing some dependencies and selecting "Validate plug-ins" returns a list of missing plugins.

This happens when you have some plugins that have more than 1 version deployed. The add action doesn't seem to be able to manage that correctly.

Reproducible: Always

Steps to Reproduce:
1. Have an environment with more that one version of a plugin available (I get the error for example with org.apache.batik where I have 1.6 and 1.7 from Orbit)
2. Press Deselect all
3. Select you main plugin
4. Make sure this results in pulling in the plugin in 1
5. Press Add required plugins
6. Now check with validate plugin that all is fine.
7. If you have more than 1 version of some plugins, they will not be added automatically (ie. it won't add the same plugin twice under different version)
Comment 1 Alain Picard CLA 2010-10-21 09:40:10 EDT
BTW, wasn't sure if this was under debug or UI, so excuse me if miscategorized.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:09:05 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.
Comment 3 Julian Honnen CLA 2019-09-09 02:30:49 EDT
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.