Eclipse plug-in migration guide
The Eclipse plug-in has recently been modified to work more closely with the CLI and the App Builder. If you are developing in trunk (published to sebring/latest), you should switch to the new plug-in as soon as possible. Here are some instructions for making your transition as seamless as possible.
Uninstall the old plug-in and update sites
To avoid problems with the Eclipse update manager, you should completely remove all traces of the old plugin. This step is necessary only if you are using a plug-in that you installed from one of these update sites:
https://www.projectzero.org/zero/silverstone/M1/update/zero.eclipse/
https://www.projectzero.org/zero/silverstone/M1/update/zero.eclipse.php/
https://www.projectzero.org/zero/silverstone/M2/update/zero.eclipse/
https://www.projectzero.org/zero/silverstone/M2/update/zero.eclipse.php/
https://www.projectzero.org/zero/silverstone/latest/update/zero.eclipse/
https://www.projectzero.org/zero/silverstone/latest/update/zero.eclipse.php/
If you are using a plug-in that came from an update site with ".rework" in the URL, you may skip ahead to the "Download and install a CLI" section.
- Uninstall any existing "WebSphere sMash" plug-ins.
- In Eclipse 3.4, go to Help > Software Updates > Installed Software.
- In Eclipse 3.2, go to Help > Software Updates > Manage Configuration.
- After a restart, remove any Update Sites that point to the old Eclipse plug-in. If you don't perform this step, Eclipse 3.4 could force the new plug-in to use the legacy Update Manger, which is not actually needed.
Download and install a CLI
If you do not have a CLI on your system, you will need to install one before the new plug-in will work. You can download the latest one from:
https://www.projectzero.org/zero/sebring/latest/download/
After downloading and unzipping the CLI,
- Open a command prompt.
- CD into the directory where the CLI is installed.
- Type 'zero'
This will bootstrap the CLI, which allows the plug-in configuration to run without an initial delay.
Install and configure the new plug-in
It is recommended, although not required, that you start with an empty workspace.
- Install the new plug-in from one of the following update sites:
- After a restart, visit the "WebSphere sMash" preferences page and enter the location of your CLI. Then select a modulegroup from the combo. Press OK.
- You should now be able to create applications, manage your repository, etc.
Users with existing workspaces
Users with existing, non-empty workspaces should do a few things before jumping back into development.
- If you had previously installed the new plug-in from silverstone/latest, delete the following directory if it exists: <workspace directory>\.metadata\.plugins\zero.cli.api\AppRoot\.zero\private\MG
- The new plug-in places different parameters in the "WebSphere sMash Application" launches, so it's in your best interest to delete and recreate the ones you use.
- You may need to update all of your projects. Do this by selecting them, Right Click > WebSphere sMash Tools > Update.
