Notable Changes in StatET RJ

RJ 4.0.0 ~ StatET 4.0.0


  • All bundles require the bundle org.eclipse.statet.jcommons.util.

  • 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:

    • org.eclipse.statet.jcommons.status
    • org.eclipse.statet.jcommons.runtime
    • org.eclipse.statet.jcommons.rmi

    (Bug 541656)

  • Large parts of the API provide nullable annotations. (Bug 539045)


  • ToolService and RToolService no longer depends on Eclipse Platform and moved to org.eclipse.statet.jcommons.ts respectively org.eclipse.statet.rj.ts.core.

  • 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)

  • The packages 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 <min>-<max>, e.g. org.eclipse.statet.rj.server.TcpPort=40100-40200. (Bug 540256)

  • The RJContext for default startup of Java based RJ servers is more flexible now:

    • It works with PathEntry instead of string path providing better support of local path as well as URLs, including URIs of nested JAR files.
    • It detects more common bundle filename patterns.

    (Bug 541791)