Eclipse p2 Director Rollback: Preserving Workspace Metadata

Eclipse p2 Director Rollback: Preserving Workspace Metadata

When a platform upgrade fails, the p2 director can reinstall or roll back installed features. The configuration area holds bundle metadata, and a snapshot can restore a functional state. However, the workspace metadata (.metadata) remains ambiguous: preserving it retains project settings but may carry corrupted state from the failed upgrade; discarding it eliminates potential corruption but loses local configuration.

Key uncertainties:

• What is the impact on build stability when .metadata is preserved after a rollback?
• Under which circumstances should the workspace metadata be discarded to avoid residual corruption?
• How can an administrator verify that the rollback succeeded without corrupting workspace settings?