Community
Participate
Working Groups
Yesterday, at the eclipse demo camp, someone suggested that launch configurations should collect the information contained in the p2.inf and use the part of it that is relevant to the launch configuration. For example, one could imagine using information like start levels, VM args and the like. Having this would avoid ppl to have to duplicate the information in two places.
+1 for implementing this issue. PDE respecting available p2.inf meta-data when creating launch configurations for e.g. products would IMHO further improve the perceived consistency of the plug-in development experience. Having to duplicate and synchronize that information between p2.inf and all the associated launch configurations (both standard and junit ones) is just plain annoying.
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.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.
