Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "StatET/Development Environment"
Line 12: | Line 12: | ||
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. | 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. | + | Workaround: |
+ | * Use OpenJDK 15 instead. | ||
[[Category:StatET]] | [[Category:StatET]] |
Revision as of 09:11, 12 October 2020
Information about development of StatET in the Eclipse IDE:
See also https://projects.eclipse.org/projects/science.statet/developer
PDE Target Platform
The target files are located in org.eclipse.statet/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 third party in org.eclipse.statet/3rdparty/_assemblies/repository/target/repository
.
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.