helios57 / goodies Goto Github PK

Create a command/handler/action to generate a workspace.properties file from the current workspace. Consider a nifty algorithm to create useful working set names. Maybe the names of the features found in workspace?

All those workspace supporting actions could be grouped under a LaunchGroup-alike button, similar to Run/Debug/Coverage, while pressing the button would execute a group of commands, the menu would contain all actions as single entries, which can be executed separately.

The parsing of a feature(.xml) is currently done "by hand", by parsing the actual feature.xml file. This is error prone. PDE provides some (unfortunately internal) API to inspect a feature plug-in. See:

PDECore.getDefault().getFeatureModelManager().findFeatureModel(featureId)

In it's current functionality, creating a workspace.properties file from the workspace will create working sets from the existing features. It would be nice to also allow a custom set of working sets.

The package contains lots of german comments. Translate those to english as well as the variables, that might be in german.

The goodies bundles should be transformed to a maven/tycho build. It might be required to add a .product bundle. No pom-files have been added so far.

Wenn ein Projekt aus der workspace.properties verschwindet (weil es obsolet ist oder weil der Branch gewechselt wird und es dort noch nicht enthalten ist), sollte es entsprechend auch aus dem Workspace entfernt werden.

Projekte, die der Anwender selber aus einer anderen Quelle dem Workspace hinzugefügt hat, die also notgedrungen niemals in der workspace.properties stehen, sollten allerdings dennoch unberührt bleiben.

Vorschlag zur Unterscheidung zwischen "obsoleten Projekten" und "fremden Projekten" im Workspace:

Wenn ein Projekt im Workspace enthalten ist und nicht in der aktuellen workspace.properties

• und der absolute Dateipfad des Projekts mit dem Pfad beginnt, in dem die workspace.properties liegt: Projekt entfernen
• der absolute Dateipfad des Projekts woanders hindeutet: Projekt unangetastet lassen

In einigen Anwendungsbeispielen kann es vorkommen, dass der Cluster-Name nicht aus + zusammengesetzt werden kann. Entsprechend ist eine komplexere Konfiguration notwendig, um zu einem Umgebungsnamen einen separaten Clusternamen angeben zu können.

The new RCS Workspace support dropdown is always disabled (or it's unclear when it is enabled) on a Windows or Linux setup.

Another Handler in the goodies should clean up the dependencies of a selected plug-in. The idea is to implement a "remove unused" dependency handler which actually verifies, if it is really the case by implicitly trying to build the bundle and check for errors.
How does BND check for import packages? How do they find references to other classes? Cn we integrate, or better, use that?
All unused plug-ins should be removed. The Manifest.fm file should be in "unsaved" mode, after the handler is done with its work, so the user can validate the changes before saving.

Extract Strings to a property file, translate them (if needed), to oxford/ghetto english and be done with.