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/0.14

List of bug fixes and enhancements in 0.14.0

New and Noteworthy

  • Tycho index files in the local maven repository and tycho in general should now be multi-process safe -- at least this is what our concurrent integration test suite is telling us.
    No more cryptic error messages when two concurrent build jobs modify the same local repository index file. Note that maven 3.0.x local repo access is still not multi-process safe.
  • In maven offline mode, tycho should now be really offline
  • tycho-surefire-plugin was ported from surefire 2.4.3 to 2.10 and now respects the surefire -DskipTests switch
  • .tar.gz has been added as a product archive format which can be built with packaging type eclipse-repository
  • Support for license features has been added
  • 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