Development/Development-Environment.adoc

+_Information about development of StatET in the Eclipse IDE_
+
+See also: https://projects.eclipse.org/projects/science.statet/developer
+
+
+== Eclipse IDE
+
+The default development environment is the Eclipse IDE with JDT, PDE and M2E.
+
+
+=== Projects / Bundles
+
+The Eclipse IDE project configurations are included in the source repository, so the projects can be imported directly as _Existing Projects into the Workspace_.
+
+
+=== PDE Target Platform
+
+The target files are located in `_releng/target-eclipse.ide/`. The target `ws-eclipse.ide` is usually suitable for the development environment ("ws" = workspace). It includes the current Eclipse installation and uses the local P2 repository for additional dependencies in `3rdparty/_assemblies/repository/target/repository`.
+
+
+=== Additional Plug-in Dependencies
+
+There are different ways to make the additional plug-in dependencies required by StatET available for the PDE build in Eclipse:
+
+  * build the P2 repository, see `CONTRIBUTING.md` (it is created in `3rdparty/_assemblies/repository/target/repository`)
+  * download the P2 repository from CI server and extract it into `3rdparty/_assemblies/repository/target/repository`
+  * install the dependencies (e.g. from a regular StatET P2 repository) into the current Eclipse installation
+
+
+=== Known Issues
+
+==== Java 11
+
+The start of the R console fails when starting/debugging StatET as Eclipse Application directly from an Eclipse workspace with StatET sources when using OpenJDK 11.
+
+The cause is that the RMI registry executable included in OpenJDK 11 accepts only jar files as codebase location, but not directories with class files.
+
+Workaround:
+
+* Use OpenJDK >= 15 instead.