Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Tycho/Release Notes/2.0

< Previous Version | Next Version >

SNAPSHOT builds

Tycho 2.0.0-SNAPSHOT is currently in development. To try out the most recent snapshot build, simply add the following snippet to your (parent) pom.xml or settings.xml, and set the property for the Tycho version (e.g. tycho-version) to 2.0.0-SNAPSHOT.

<pluginRepositories>
    <pluginRepository>
      <id>tycho-snapshots</id>
      <url>https://repo.eclipse.org/content/repositories/tycho-snapshots/</url>
    </pluginRepository>
</pluginRepositories>

SNAPSHOT site docs

Refer to the latest SNAPSHOT site docs for Tycho and Tycho Extras.


New and Noteworthy

Complete list of bug fixes and enhancements in 2.0.0-SNAPSHOT

Java 11

  • Tycho now requires Java 11 as a minimum runtime requirement
  • The default execution environment (EE) for the tycho-eclipserun-plugin was also bumped to Java 11
  • The default source and target settings for the tycho-compiler-plugin were also bumped to Java 11

Requires Maven 3.6.3 or more recent

Resolve system.packages from Execution Envionment against toolchain or current JRE, from Java 13

bug 563930 Since Java 9 and module JVM, JREs can now have different sets of system packages from the same version. As a result, the list of system packages cannot be built statically. So Tycho will now query the defined toolchains when to get the actual system packages when requested (mainly for the tycho-compiler-plugin when requireJREPackageImports=true). If no matching toolchain is found, a warnign is emitted and the current Java runtime is used.

An error-prone workaround was implemented in Tycho 1.x for Java 9 and 11, with a static list of system packages. This workaround is still active for those Java version, but not for newer Java versions; but we may decide to remove the workaround in a near future (maybe even before 2.0 releases) to bring more consistency and correctness.

Back to the top