Bug 309218

Description Martin Oberhuber 2010-04-14 16:42:45 EDT

+++ This bug was initially created as a clone of Bug #305716 +++

The Unittests for fast project import from snapshot need to be enhanced to also check handling of Linked Resources.

Acceptance criteria:
- Linked resource pointing to an absolute path outside the workspace
  with content: exported snapshot includes content under the absolute path,
  such that import with snapshot faithfully restores the original project.
  ==> Since "reconcileLinks" needs to be done on project import, we may
      need to take care of what happens when (a) the actual absolute path
      does not exist on import from snapshot, or (b) a Windows style absolute
      path was exported but is then imported on Linux.

- Linked resource pointing to a path relative to the project but outside
  the workspace: exported snapshot includes content, project structure is
  faithfully restored -- basically same behavior expected as if the 
  relatively linked resources were directly under the project.

- Linked resource using a Preference Path Variable pointing outside the WS:
  ==> snapshot includes data under the linked resource. On import, when the
      path variable exists, content is restored. 
  ==> When the path variable is not defined on import, I'm unsure what to 
      do (supposedly not import the tree but mark as a broken linked 
      resource. Or, import the tree first but then reconcile links into a
      broken linked resource).

- Linked resource pointing to a different project (==Alias): content under
  that linked resource is not exported to snapshot since that content is
  considered to be owned by the other project.
  ==> Import without the other project open creates a broken linked resource
  ==> Import with the other project open doesn't lead to extra refresh

Rather than writing Unittests for this right away, we could also easily manually check these scenarios once the UI for import/export with snapshot is done as per bug 303751. In that case I'd expect a workspace with all the special cases mentioned above to be exported with snapshot and attached here on the bug, such that it can be imported with or without snapshot by somebody else for verification.