|[p2-dev] p2 development branch and associated PDE changes|
I've just released changes to the R3_6_api_cleanup development branch that affect the way restarts are handled. 
However, this code requires changes PDE UI. The required changes are documented in a dependent PDE bug .
For p2 developers, this means that if you are developing/running code against the branch, you'll need to load org.eclipse.pde.ui into your workspace and apply the patch in the PDE bug.
It's going to be messy managing a bunch of dependent component patches while we work in the p2 branch. I talked to Curtis today about creating a PDE branch that will hold the changes caused by the p2 branch. This way, the PDE team could commit p2-related changes as we go, and those on the bleeding edge of the p2 work can develop against the PDE branch (and any other projects where we hit this problem.)
I'm also wondering if we'll have a way to initiate a build against the relevant branches. I spent a lot of time dealing with self-hosting pain while trying to test these changes. I realize we can "export into target" but in my particular case, the PDE code I was touching *was* the export into target code, so I broke my own export until getting the code right. This was painful.