The eclipse commandlet allows to install, configure, and launch the Eclipse IDE.
To launch Eclipse for your current workspace and devonfw-ide installation simply run:
devon eclipse
You may also supply additional arguments as devon eclipse «args». These are explained by the following table:
devon eclipse| Argument(s) | Meaning |
|---|---|
|
if provided as first arg then to command will be invoked for each workspace |
|
setup Eclipse (install or update) |
|
install an additional plugin |
|
launch Eclipse (default if no argument is given) |
|
same as |
|
update workspace |
|
reverse merge changes from workspace into settings |
|
reverse merge adding new properties |
|
create launch script for this IDE, your current workspace and your OS |
During the setup devon eclipse setup will be called what automatically installs Eclipse. The project configuration typically defines the plugins that will be installed via ECLIPSE_PLUGINS variable. Otherwise defaults from this eclipse commandlet will apply.
However, for specific needs you may even install additional plugins. In general you should try to stick with the configuration pre-defined by your project. But some plugins may be considered as personal flavor and are typically not predefined by the project config. This e.g. applies for devstyle that allows a real dark mode for eclipse and tunes the theming and layout of Eclipse in general. To avoid that projects ship with
too many plugins that may waste resources but are not used by every developer you have the freedom to install some additional plugins. Be aware that this comes at your own risk and sometimes plugins can conflict and break your IDE. The following list of plugins is guaranteed to be supported by this commandlet:
-
cobigen (incremental code-generator)
-
anyedit (for easy compare with clipboard, etc.)
-
checkstyle (for checkstyle support)
-
spotbugs (successor of findbugs)
-
startexplorer (for support to open current item in file manager of your OS)
-
terminal (open terminal/shell inside Eclipse as view)
-
github (for devonfw projects that want to access github issues in Eclipse)
-
soapui (for service testing)
-
regexutil (to test regular expressions)
-
templatevariables (for advanced JDT templates)
The link-titles are the IDs accepted by devon eclipse add-plugin «id». Otherwise the full featureID has to be specified together with the URL of the update site. However this is intendet for project specific configuration. Here is an example how a project can configure the plugins in his devon.properties inside the settings:
ECLIPSE_PLUGINS=("AnyEditTools.feature.group" "http://andrei.gmxhome.de/eclipse/" "com.ess.regexutil.feature.group" "http://regex-util.sourceforge.net/update/")For the above listed plugins you can also use the short form:
ECLIPSE_PLUGINS=("anyedit" "" "regexutil" "")Of course you may also mix plugin IDs with fully qualified plugins.