Community
Participate
Working Groups
when you setup a launch config with features PDE appears to compute the list of bundles by something akin to Add Required Plugins with optional and fragments on. This sometimes gets too much stuff. For exmaple, if you are trying to do feature-based testing withOUT the optional bit, you just can't do it. It would be interesting if the bundle list computation was basically the same as that done for feature based product launching. This would also enable a (somewhat circuitous) workflow for testing products whereby the user creates their product but duplicates the set of features in a feature-based Junit plugin launch config and adds their tests. I'm marking this a "major" as it blocking our ability to test various configurations. Creating plugin-based configs is a workaround but would be a significant hassle as the structure is quite complicated.
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 ***
