Community
Participate
Working Groups
There are a few use cases where this method would be useful. We are already using this internal method in our preference pages. I'm not aware if there was a reason why this was excluded from the provisional API, but I think we can justify including it. Case #1: Trying to restore things after messing with the target. After changing the target platform to perform some operation, the client may want to restore the default state of the target platform. Currently there is no practical way to do this except to store the previous target themselves or browsing the list of known targets. Case #2: Trying to see if a target definition is equivalent to the default target. This is the case that our preference page encounters and uses the method for. Knowing whether the target is default can prevent duplicates from being created and provide UI improvements. Note that even with changes to support multiple targets, this would be a useful feature.
Ankur, this could be added to the branch or after the changes are merged.
Target API is waiting for M4
Fixed in master http://git.eclipse.org/c/pde/eclipse.pde.ui.git/commit/?id=ea5191af3304c437f0116f174474bfbd1085376d
Verified in I20111206-1015