Bugzilla – Full Text Bug Listing
| Summary: | [patch] Should read start levels from bundles.info of target platform when launching Eclipse application | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Gunnar Wagenknecht <gunnar> | ||||
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> | ||||
| Status: | RESOLVED WONTFIX | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | darin.eclipse, jeffmcaffer | ||||
| Version: | 3.6 | ||||||
| Target Milestone: | 3.7 | ||||||
| Hardware: | PC | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Gunnar Wagenknecht
Created attachment 170514 [details]
patch for reading custom start levels from targ platform bundles.info
The attached patch adds the ability to read "non-default" start level settings from the target platform and uses them when assembling the bundles.info for the Eclipse application launch.
This should be a 3.6.1 candidate. PDE team, please unset target milestone if you think it shouldn't. Moving to 3.7. I view this as new function rather than a bug/maintenance fix to existing function. This one is a little difficult. The current patch assumes that if there is configuration information in the target then it should be used. This is great in particular situations but not in all. some how we need to know if that is the user's intention or not. Related, will this result in a situation where different users will get different launch behaviors depending on their target? That is, will the same .launch file in my workspace and yours yield the same actual launched configuration? (In reply to comment #4) > Related, will this result in a situation where different users will get > different launch behaviors depending on their target? That is, will the same > .launch file in my workspace and yours yield the same actual launched > configuration? That is a good point. My original use case for creating this patch was to make it easier for consumer of my target platform to launch it. But I guess other then documenting required start levels I'm out of luck here until p2 could inject such configurations into any target platform. In the end what I would really like is for p2 to be used to "install" the thing that we are about to launch. Perhaps there is something we can do with a fake engine or something that would go through the motions of installing but really only create all the configuration settings. We're a ways off that though... |