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

Bug 313275

Summary: [doc] - mention need to include and start ds when using p2, PDE build
Product: [Eclipse Project] Equinox Reporter: Susan McCourt <susan>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: pascal, rancidfishbreath, tjwatson
Version: 3.6Keywords: Documentation
Target Milestone: 3.6 RC4   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Susan McCourt CLA 2010-05-18 00:29:47 EDT 
I don't recall if we have a bug to capture the discussion about the use of ds in p2 in http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg06180.html

Pasting in the relevant comments here.  We need to ensure the readme, migration guide, etc. mention the use of DS.

---------------------------------------

I can appreciate the desire to allow different DS implementations but the bottom line is that DS is going to break any RCP application that uses P2 (there may be other fall out as well).  My RCP app uses P2 so I thought that I should download 3.6M5 so that I had time to make comments about the API before the API freeze.  When I updated not only did my auto update functionality break, but my build server broke also (PDE build with P2).  It took 6 weeks of googling before I figured out that there was this new DS bundle that I not only had to include, but I also had to be responsible for starting.

All is well for me now, but I fear that this change is going to have a big impact when 3.6 releases.  At a minimum this needs to be documented probably both in "What's New" in the "Plug-In Development Environment Guide" and also in the 3.6 Plug-in Migration Guide.  Getting the rcpupdate example updated (bug 307558) was a good step in the right direction.
Comment 1 John Arthorne CLA 2010-05-31 15:11:03 EDT 
Without seeing this bug I added something about this in the platform migration guide this morning. I mentioned ds needs to be included and started, and added a pointer to our provisional API migration guide on the web.
Comment 2 Thomas Watson CLA 2010-06-02 16:03:03 EDT 
*** Bug 308839 has been marked as a duplicate of this bug. ***