While working with the workspace containing the Scout demo applications, I have a lot of projects inside. The Scout Explorer presents a logical representation of each application. However, to access some files (like the MANIFEST.MF file) you have to use the Package Explorer View.
A possibility is to group the projects corresponding to one demo application into a separate working set.
Of course you can work with PSF files (we have started to propose PSF files for each application), but there are still a lot of manipulations needed to import them correctly into the workspace. (See our current how to Download and Run Locally the Scout Demo Application).
During the last EclipseCon Europe I was told that a couple of good tools were provided by the CDO project. Dynamic working sets is one of them. It allows to define rules, to assign projects into a working set. Rules are based on predicates describing the project (name, pattern, nature, builder, file …) and logical operator predicates (and, or, not…).
Install the “CDO Release Engineering Dynamic Working Sets” feature from one of the update site:
See the CDO download page to find the release corresponding to your Eclipse version.
After a restart, you can start to define your dynamic working sets.
In the Preferences dialog navigate to: Release Engineering > Dynamic Working Sets. Click on the “Edit Button”.
The “Dynamic Working Set Preferences” editor is opened in the Eclipse Workbench. Users familiar with EMF will make themselves at home.
The editor is simple to use. It represents the working sets as a tree. First level nodes correspond to the working sets and sub-level nodes are the combinations of predicates to collect the projects.
At the top level node, select “New Child > Working Set”.
The name of the new created working set can be defined in the Properties view. To add the first predicate you select again: “New Child > Name Predicate”
Again in the Properties view you can set a Pattern. For the BahBah Chat Application we want to collect all projects with the name matching org.eclipsescout.bahbah.*
Finally you get a tree defining the working sets as follow:
After having saved the modifications in the editor the working sets are created. You can display them by choosing “Top level elements > Working sets” in the menu.
Here is the result:
I haven’t found out how to import and export the configuration file. I was hoping to find an export and an import button in the preference page.
Eike Stepper recommends to use a recent version (integration or nighly build) of the Dynamic Working Sets feature, because a lot of bugs were fixed.