Skip to main content
Jump to: navigation, search

Tycho/Release Notes/0.16

< Tycho‎ | Release Notes
Revision as of 08:05, 10 April 2013 by (Talk | contribs) (grouped new&noteworty by topic (like on the 0.17 page))

New and Noteworthy

Complete list of bug fixes and enhancements in 0.16.0


Target Platform & Dependency Resolution

  • A new packaging type "eclipse-target-definition" for PDE target definitions has been added
  • 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).
  • With Tycho 0.15, if a composite site was loaded as part of the target platform resolution for a build, and some of the child sites were missing, a warning would be logged but the build would continue. With Tycho 0.16.0, the build instead fails. To recover the old behaviour, add this property to your composite*.xml files. See also [1], [2]:
    <property name="p2.atomic.composite.loading" value="false"/>
  • Added a property "tycho.localArtifacts" 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 command line and in settings.xml. (See also this section in the target platform documentation.)
    • if unset (or set to "default"), the behaviour is unchanged (local metadata is considered by the resolver, and there is a warning if locally built units were used)
    • if set to "ignore", locally built artifact are ignored
  • Basic support for custom execution environment profiles (bug 385930)
  • 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

Test Execution

  • 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

    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.

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



  • 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

Back to the top