Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313955 - feature based launching uses only one version of junit.source
Summary: feature based launching uses only one version of junit.source
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-21 14:12 EDT by Darin Wright CLA
Modified: 2019-09-09 02:43 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Wright CLA 2010-05-21 14:12:10 EDT 
3.6 RC2

* Create an Eclipse Application launch configuration that is feature based
* Select the org.eclipse.sdk feature and all required features

When launching, only one version of org.junit.source is included in the launch, when both should be included. The version that gets included sometimes changes from 3.8.2 to 4.8.1.

I noticed this as it causes the target state to be discareded/re-created when launching. Theoretically, the target state should be consistent from launch to launch if no changes are made to the bundles/features being launched.
Comment 1 Curtis Windatt CLA 2010-05-21 14:17:49 EDT 
Ankur, please look at this when you get a chance.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:03:29 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:43:02 EDT 
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.