Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315061 - [patch] Should read start levels from bundles.info of target platform when launching Eclipse application
Summary: [patch] Should read start levels from bundles.info of target platform when la...
Status: RESOLVED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: 3.7   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-31 07:28 EDT by Gunnar Wagenknecht CLA
Modified: 2010-12-13 21:14 EST (History)
2 users (show)

See Also:


Attachments
patch for reading custom start levels from targ platform bundles.info (4.77 KB, patch)
2010-05-31 07:36 EDT, Gunnar Wagenknecht CLA
gunnar: review?
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Gunnar Wagenknecht CLA 2010-05-31 07:28:13 EDT
3.6

When launching an Eclipse application PDE should support reading start levels from the target platform bundles.info. This is especially useful when working with non-product based target platforms.
Comment 1 Gunnar Wagenknecht CLA 2010-05-31 07:36:20 EDT
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.
Comment 2 Gunnar Wagenknecht CLA 2010-05-31 07:41:26 EDT
This should be a 3.6.1 candidate. PDE team, please unset target milestone if you think it shouldn't.
Comment 3 Darin Wright CLA 2010-06-07 09:45:41 EDT
Moving to 3.7. I view this as new function rather than a bug/maintenance fix to existing function.
Comment 4 Jeff McAffer CLA 2010-12-13 10:19:25 EST
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?
Comment 5 Gunnar Wagenknecht CLA 2010-12-13 16:38:14 EST
(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.
Comment 6 Jeff McAffer CLA 2010-12-13 21:14:33 EST
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...