Skip to main content
Jump to: navigation, search

Tycho/Release Notes/0.19

< Tycho‎ | Release Notes
Revision as of 08:25, 18 October 2013 by (Talk | contribs) (reformatted (use html tags so that pre are indented within lists))

< Previous Version | Next Version >

Tycho 0.19.0 is currently under development. This page shows a preview of features which will be available in the 0.19.0 milestone.

List of bug fixes and enhancements in 0.19.0


To try out the most recent snapshot build of 0.19.0, simply add the following snippet to your (parent) pom.xml, and set the property for the Tycho version (e.g. tycho-version) to 0.19.0-SNAPSHOT.


SNAPSHOT site docs

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

New and Noteworthy

Test Execution

  • Add experimental support for test runtime provisioned by p2. This can be used for integration test scenarios which require a fully provisioned application (including root files, start levels, etc.), same as it would be delivered to customers.
    Example: To install product under test with ID "", test bundle and tycho surefire test harness bundles using the p2 director, use the following pom.xml snippet in the test module:
                <!-- add dependency  to product IU under test -->

    Note that testRuntime=p2Installed currently only works when testing products. You can also run tests on existing product archives built elsewhere. To do this, just make sure to extract the product archive into target/work before the tests are run(i.e. in a phase prior to integration-test). See docs <TODO link to maven site> for details.

  • Add suppport for 'runOrder' parameter in tycho-surefire-plugin to run tests in random order (bug 409923)


  • tycho-version-plugin:set-version now also updates versions of exported packages, when the packages have the same version as the bundle version without qualifier.
  • Reproducible version qualifiers based on git commit timestamps (bug 402949)
    • (INCOMPATIBLE CHANGE) By default, any uncommitted local changes will now fail the build (this was never meant to be supported)
    • Configuration option jgit.dirtyWorkingTree allows to control behaviour in case of uncommitted changes detected for a module:
      • error (default): fail the build if git status is not clean. This is useful for production builds to make sure the commit timestamp build qualifier used is really reproducible
      • warning: warn about any uncommitted changes and use the current build timestamp as build qualifier for the "dirty" module. This is useful for local builds with uncommitted changes.
      • ignore: do not check whether git status is clean and use the timestamp of the last git commit as build qualifier. This can be used in case jgit should report a false positive dirty working tree.
    Sample configuration:
  • Port tycho's JDT compiler to maven-compiler-plugin 3.x (bug 405385)

Back to the top