AppEnvironment is enhanced and provides bundle resolution now.
RJContext uses the AppEnvironment for bundle resolution by default. Applications need to be adapted.
org.eclipse.statet.jcommons.util provides tools for bundle resolution in different types of application. Automatic setup of the application environment is supported for
RJContextfor default startup of Java based RJ servers changes. Applications which use
RJContext.searchRJLibsdirectly or extends the class need to be adapted. (Bug 559616)
All bundles require the bundle
All bundles, except bundles of eclient, no longer depends on Eclipse Platform. This includes that bundles of ecommons or an ‘eruntime’ bundle are no longer required.
This causes various changes in the method signatures of the API. New relevant packages are:
Large parts of the API provide nullable annotations. (Bug 539045)
RToolService no longer depends on Eclipse Platform and moved to
The new method
RService.findData finds the first object with a specified name in environments and returns a fully qualified object with the object itself and the environment where the object is found. (Bug 540153)
org.eclipse.statet.env.* provide common classes for R environment and R pkg management as known from the StatET IDE.
The newly introduced system property
org.eclipse.statet.rj.server.TcpPort allows to configure the TCP ports used by RJ servers. The range must be specified by a value
org.eclipse.statet.rj.server.TcpPort=40100-40200. (Bug 540256)
RJContext for default startup of Java based RJ servers is more flexible now:
PathEntryinstead of string path providing better support of local path as well as URLs, including URIs of nested JAR files.