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.16

< Previous Version | Next Version >

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

SNAPSHOT builds

To try the most recent snapshot build of 0.16.0, simply add the following snippet to your (parent) pom.xml and set tycho version to 0.16.0-SNAPSHOT.

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

List of bug fixes and enhancements in 0.16.0

New and Noteworthy

New Features

  • Support for parallel test execution with JUnit >= 4.7 has been added.
    If you use Junit >= 4.7, you can now have test classes or methods executed by several threads in parallel by adding -Dparallel=classes|methods|both on the commandline or by configuring
    <plugin>
       <groupId>org.eclipse.tycho</groupId>
       <artifactId>tycho-surefire-plugin</artifactId>
       <version>${tycho-version}</version>
       <configuration>
         <parallel>classes|methods|both</parallel>
       </configuration>
    </plugin>
    

    Executing tests in parallel can be useful e.g. if you have long-running integration tests which are not CPU-bound.
    Under the hood, this feature was enabled by porting the junit4.7 surefire provider to Tycho.

  • Reproducible Version Qualifiers
  • A new plugin to validate target platforms. This plugin takes as input one or several target platforms and ensures they can be resolved, fails otherwise
    <plugin>
       <groupId>org.eclipse.tycho.extras</groupId>
       <artifactId>target-platform-validation-plugin</artifactId>
       <version>${tychoExtrasVersion}</version>
       <executions>
          <execution>
             <phase>validate</phase>
             <goals>
                <goal>validate-target-platform</goal>
             </goals>
             <configuration>
                <targetFiles>
                   <param>indigo.target</param>
                   <param>juno.target</param>
                </targetFiles>
                <failOnError>true</failOnError>
             </configuration>
          </execution>
       </executions>
    </plugin>

Improvements and Fixes

  • If several tycho versions were inadvertently mixed within the same reactor, this could lead to cryptic errors like ClassCastExceptions. This situation is now detected early and the build will fail with a clear error message
  • Providing credentials for a p2 repository specified in a target file is now more convenient – the use of the non-standard id attribute in target files is no longer necessary (bug 377086).
  • Access to p2 repository can be redirected to a mirror location. This now works for both target files and repositories specified in the POM (bug 356016).
  • tycho-compiler-plugin now has a boolean option requireJREPackageImports which will fail the build if set to true and packages provided by the JDK are not explicitly imported.
    This is the design-time equivalent of setting equinox runtime option osgi.compatibility.bootdelegation=false.
  • Support for test frameworks is extensible now. This means you can add support for test frameworks other than JUnit if you provide an implementation of TestFrameworkProvider.
  • The tycho-p2-director-plugin can now create product installations which have meta-requirements on the installer. This for example allows to execute custom touchpoint actions during the installation. See the integration test for an example.
  • Added a property "tycho.considerLocal" which allows to control whether artifacts installed in the local maven repository by previous tycho builds should be considered by the resolver or not. The property can be specified on the commandline and in settings.xml.
    • if not set, behaviour is unchanged (local metadata is considered by the resolver, but warn if local-only IUs were used)
    • if set to true, consider local metadata and do not warn about usage of locally installed IUs
    • if set to false, ignore local-only metadata

Complete list of bugs marked for 0.16

Back to the top