Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

If you have a standard set of projects that you import into every workspace, you can install the project importer workspace mechanic plugin and automate that process. Just drop config files with a .proj extension into your ~/.eclipse/mechanic folder.

Install Site

http://webobjects.mdimension.com/mechanic/

Source

The source is distributed as part of WOLips, though there aren't any dependencies on any other plugins in WOLips.https://github.com/wolips/wolips/tree/master/wolips/core/plugins/org.objectstyle.wolips.mechanic

~/.eclipse/mechanic/YourFile.proj Format:

Code Block
# @title the title of your task
# @description the description of your task
# @reconcile true or false; reconcile true means that all of the discovered projects are checked every time, false means it does one initial installation and then never checks for changes
/Path1
/Path2
/Path3

Example 1

You can define one or more paths to your projects. This can either be a path that points to a single project, or a path that points to a folder containing projects. When you point to a folder containing projects, note that the importer will not scan below the direct children of the folder.

Code Block
# @title A Bunch of Projects
# @description Import a bunch of projects into this workspace
# @reconcile true
/Absolute/Path/To/Projects

Example 2

If you use a relative path, it will be relative to your workspace folder.

Code Block
# @title Relative Projects
# @description Import a bunch of projects based on a relative path
# @reconcile true
../RelativePathContainingProjects

Example 3

You can define multiple entries, with a mix of absolute, relative, and container folder references.

Code Block
# @title Individual Projects
# @description Import Wonder 2.0/5.4 into this workspace
# @reconcile true
/Path/To/Project1
/Path/To/Project2
/Path/To/FolderContainingProjects