Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 71131

Summary: [plan item] RCP support
Product: [Eclipse Project] PDE Reporter: Jim des Rivieres <jeem>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P4 CC: bernard.lumbroso, bogofilter+eclipse.org, djb, dorisviv, ed.burnette, evan.williams, jeffmcaffer, kehn, Konstantin.Scheglov, sascha.gaertner, scottf, vimalvachhani
Version: 3.0Keywords: plan
Target Milestone: 3.1 M6   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on: 49592, 53439, 53468, 60000, 72678, 73541, 73818, 73820    
Bug Blocks:    

Description Jim des Rivieres CLA 2004-07-29 17:57:03 EDT
PDE currently supports developing Eclipse plug-ins, but is not expressly 
geared for the specific needs of clients developing applications based on the 
RCP. PDE should facilitate developing and deploying RCP-based applications.
Comment 1 Morten Christensen CLA 2004-09-01 05:23:27 EDT
PDE support for RCP will indeed be a VERY good thing! 

Besides the proposed PDE support for RCP I was also
thinking of making the PDE aware of general
RCP-compatiblity issues of eclipse plugins.

In particular, I am thinking about compability 
between general plugins written for the normal eclipse
IDE 3.0 (for software developers) and new
applications based on Eclipse RCP.

I imagine that some (but definitely not all) general 
plugins for the "normal" eclipse IDE may also be useful
for some applications based on the RCP.

For example a "XML editor" plugin may be useful for both 
the "normal" eclipse IDE AND for a number of rich clients
based on the eclipse platform. 

Therefore, even for non-RCP plugin-work the PDE should be able
to warn if plugins are using references to IDE-only objects
that will cause the plugin to be incompatible with RCP.
Comment 2 Wassim Melhem CLA 2004-09-14 01:17:50 EDT
*** Bug 71063 has been marked as a duplicate of this bug. ***
Comment 3 Wassim Melhem CLA 2004-09-14 01:30:08 EDT
This item will be marked as resolved when the following bugs/features are addressed:

bug 49592: RCP deployment solution.
bug 53468: Enhance the New Plug-in Project wizard to create new RCP apps (done).
bug 60000: A comprehensive RCP template
bug 73818: Product tooling and branding
bug 73820: Contextual runtime workbench launches.
bug 72678: Support branding/splash screen when launching RCP apps.
Comment 4 Wassim Melhem CLA 2004-09-14 01:40:47 EDT
Two more items of relevance to this plan item:
bug 73541: Introduce the notion of a PDE "working set", which would greatly
simplify the task of hand-selecting plugins for RCP testing.

bug 53439: Introducing an on-demand validation function to the runtime workbench
launch configuration to ensure that the list of plugins selected by the user is
complete,  etc.  This function would use the Platform/Runtime state so all
problems that might be encountered at startup can be foreseen before launching.
Comment 5 Ron Baldwin CLA 2004-09-14 11:08:25 EDT
Can these be added to the list of dependent bugs?  Also, is it ok for
non-eclipse devs to set the depends and blocks fields?
Comment 6 Wassim Melhem CLA 2004-09-14 15:36:00 EDT
Added the dependencies as requested.
Fields that must not be used by non-developers are the Priority and Target 
Milestone.

As for the depends/blocks, I'm not sure.  Perhaps Jim knows more about 
bugzilla process/etiquette.
Comment 7 Juergen Weber CLA 2004-09-15 04:29:33 EDT
See also Bug 70198
Comment 8 Wassim Melhem CLA 2005-03-16 15:52:03 EST
This plan item is complete as we now have a solid story for RCP development 
and packaging.  It also includes the successful resolution of bug 85153.

Of course, we always welcome additional feature requests.  If you have any, 
please open separate bug reports and they will be evaluated on an individual 
basis.
Comment 9 Wassim Melhem CLA 2005-03-16 15:52:49 EST
Jim, please update the project plan item entry accordingly.  thank you.