Skip to main content
Jump to: navigation, search

Tycho/Release Notes/0.14

< Tycho‎ | Release Notes
Revision as of 11:25, 21 December 2011 by T-oberlies.posteo.de (Talk | contribs) (fix introduction; link to Igor's announcement of the snapshot build results; some formatting)

Tycho 0.14.0 is currently in development. This page shows a preview of features which will be available in the 0.14.0 release.

List of bug fixes and enhancements in 0.14.0

0.14.0-SNAPSHOT versions

Currently, there are no official snapshot versions of Tycho available (see bug 360628).

As a workaround, Sonatype Inc. provides an additional CI build of the Tycho sources and makes that result available in this Maven repository. To use this CI build result, add the following snippet to your (parent) POM and set Tycho version to 0.14.0-SNAPSHOT.

<pluginRepositories>
  <pluginRepository>
    <id>tycho-snapshots</id>
    <url>https://oss.sonatype.org/content/groups/public/</url>
  </pluginRepository>
</pluginRepositories>

New and Noteworthy

  • Full support for bundle runtime execution environments
    • List of accessible system packages of bundle runtime execution environment is now respected during project dependency resolution and java compilation. This makes sure that bundles do not accidentally reference JRE classes that may not be available in all runtime environments supported by the bundles.
    • If bundle project supports multiple runtime execution environments, Tycho will use the list of packages from the most restricted environment by default. Build target execution environment can be specified explicitly using new <executionEnvironment> target platform configuration parameter. For backwards compatibility with PDE, jre.compilation.profile build.properties property is supported too.
    • Additionally, tycho-compiler-plugin can be configured to use different JDK libraries for different bundle runtime execution environment. Additional JDKs are configured using Maven toolchains.xml, where toolchain id element is matched to execution environment profile name. For example
 <toolchains>
  <toolchain>
     <type>jdk</type>
     <provides>
         <id>J2SE-1.5</id>
     </provides>
     <configuration>
        <jdkHome>/path/to/jdk/1.5</jdkHome>
     </configuration>
  </toolchain>
 </toolchains>

Back to the top