WebSphere Application Server - IBM Redbooks

Tip: If you want to skip the option box, but would like to change workspaces,
you can start Studio Site Developer with the following command:
wasexpress -data workspace_name
For example:
wasexpress -data c:\user-workspace
If the workspace directory does not exist, it will be created.
If you have sufficient memory available on your workstation, it is possible to
execute multiple instances of Studio Site Developer running simultaneously
using different workspaces. This technique is useful, for example when working
on two releases of a project at the same time, such as building a new release and
performing maintenance on an old one. Each development branch can have its
own workspace and copies of the project files.
3.1.1 Recovering files from their local history
When working with Studio Site Developer, there are two things to remember:
► All deletes are permanent. There is no recycle bin.
► A history of all changes is maintained locally and files can be reset to a
previous state.
A history of all files that you have changed is cached locally. This allows you to
compare a resource with a previous version and, if required, replace it with that
version. The local history of each file is updated when you create or modify a file.
Each time you save a file, a copy of its previous state is also saved. A new history
for a resource is created the first time you modify the base version of it.
This allows you to compare the current file state to a previous state and to
replace the file with a previous state. Each state in the local history is identified
by the date and time the file was saved.
Note: Only files have local histories, not projects or folders.
Comparing a file to the local history
To view the local history of a file, select the file in the navigator view, right-click,
and select Compare with -> Local History from its context menu.
Chapter 3. Using Studio Site Developer 45