[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[p2-dev] Fw: Major UI refactoring released to API branch - things may be broken this week
- From: Susan Franklin McCourt <susan_franklin@xxxxxxxxxx>
- Date: Thu, 12 Nov 2009 10:52:10 -0800
- Delivered-to: email@example.com
the UI is no longer broken, and the related PDE changes have been released into the branch.
All UI tests are passing, and smoke tests involving install, update, uninstall, and revert are working as expected.
There is still work to do/oddities
- many, many strings were moved around, so it's possible there's a progress task message missing or similar issues
- I'm still working in the area of batching core events. So you'll see oddities with the "work with:" combo flashing, etc.
- the API itself still needs javadoc work and some cleanup.
If you are running the UI in the branch, please open bugs on anything odd you see, and make sure you mention that you are in the branch.
----- Forwarded by Susan Franklin McCourt/Beaverton/IBM on 11/12/2009 10:46 AM -----
I've committed a bunch of changes to the p2 UI in support of some API requests .
The overall direction looks quite promising, but the UI will be a bit broken for a few days until we sort out some service registry and ds issues.
If you run a self hosted p2 UI from the branch, here are some things you need to know.
1. There is a new p2 bundle and also a new branch of org.eclipse.ui.ide.
You can get these by reloading the project sets
2. There are required changes to PDE UI documented in . This doesn't matter if you aren't going install into the self profile of your self hosted workbench or run PDE target definition code. You'll need to include the patch from this bug until the PDE guys can commit them to the branch
3. I've been able to install and uninstall releng tools using the new code, but there are some problems that are immediately noticeable:
- IUPropertyUtils is unable to obtain a profile registry, so translations are not found
- the SDK policy registration via ds is failing, so the default policy is used instead.
4. The ui tests do not all pass yet. I'm investigating these.