| Summary: | Launching with features should not add optional things | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Jeff McAffer <jeffmcaffer> |
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | ankur_sharma, curtis.windatt.public, darin.eclipse, rune.glerup, sgandon |
| Version: | 3.7 | ||
| Target Milestone: | 3.7 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Jeff McAffer
Bringing it on 3.7 radar Would it make sense to add a check box option that is used to include optional dependencies? Seems to me that sometimes people will want to test without optional bundles, and sometimes will want to test with the optional bundles. Sure. How are fragments treated in this? In a regular launch config there is a check box for optional dependencies but no mention of fragments (I vaguely recall that there used to be something). Are fragments considered as "optional"? in any event, an option that gives the same behaviour as a product launch would be great (however it is worded) *** Bug 331202 has been marked as a duplicate of this bug. *** Marking as a duplicate of a newer bug with a patch. *** This bug has been marked as a duplicate of bug 338078 *** |