This page shows a preview of features which will be available in the 0.19.0 milestone.

+

−

[https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&product=Tycho&query_format=advanced&resolution=FIXED&target_milestone=0.19.0&order=bug_id&query_based_on= List of bug fixes and enhancements in 0.19.0]

+

[https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&product=Tycho&query_format=advanced&resolution=FIXED&target_milestone=0.19.0&order=bug_id&query_based_on= Detailed list of bug fixes and enhancements in 0.19.0]

== New and Noteworthy ==

== New and Noteworthy ==

+

+

=== Target Platform & Dependency Resolution ===

+

+

* (INCOMPATIBLE CHANGE) The syntax for specifying profile properties during dependency resolution was changed to the normal <tt>&lt;key&gt;value&lt;/key&gt;</tt> syntax. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=412283 bug 412283] for an example.

+

* (INCOMPATIBLE CHANGE) <tt>system</tt>-scoped pom dependencies will now be ignored if used with <tt>pomDependencies=consider</tt> ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=415774 bug 415774]). <br/>This corner case was supported only half-way anyway. If you absolutely have to use local-only jars with <tt>pomDependencies=consider</tt>, use e.g. [http://maven.apache.org/plugins/maven-install-plugin/ mvn install:install-file] instead which will allow to reference them as normal (compile-scoped) pom dependencies without a hardcoded filesystem path.

+

* <tt>Bundle-ClassPath: external:...</tt> MANIFEST entries in referenced bundles no longer fail the build, but will be ignored with a warning now ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=370958 bug 370958])

+

* The logging of download problems for artifacts from p2 repositories has been significantly improved.

+

+

=== Test Execution ===

+

+

<p><ul>

+

<li> Add experimental support for test runtime provisioned by p2.<br/> 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.

+

<br/>Example: To install product under test with ID "example.product.id", test bundle and tycho surefire test harness bundles using the p2 director, use the following pom.xml snippet in the test module:

+

<pre>

+

<plugin>

+

<groupId>org.eclipse.tycho</groupId>

+

<artifactId>tycho-surefire-plugin</artifactId>

+

<version>${tycho-version}</version>

+

<configuration>

+

<testRuntime>p2Installed</testRuntime>

+

</configuration>

+

</plugin>

+

<plugin>

+

<groupId>org.eclipse.tycho</groupId>

+

<artifactId>target-platform-configuration</artifactId>

+

<version>${tycho-version}</version>

+

<configuration>

+

<dependency-resolution>

+

<extraRequirements>

+

<!-- add dependency to product IU under test -->

+

<requirement>

+

<type>p2-installable-unit</type>

+

<id>example.product.id</id>

+

<versionRange>0.0.0</versionRange>

+

</requirement>

+

</extraRequirements>

+

</dependency-resolution>

+

</configuration>

+

</plugin>

+

</pre>

+

+

Note that <tt>testRuntime=p2Installed</tt> 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 <tt>target/work</tt> before the tests are run(i.e. in a [http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Lifecycle_Reference phase] prior to <tt>integration-test</tt>).

+

See [http://eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/test-mojo.html#testRuntime site docs] for details.

+

</li>

+

<li> Add suppport for [http://eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/test-mojo.html#runOrder runOrder] parameter in tycho-surefire-plugin to run tests in random order ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=409923 bug 409923])</li>

* (INCOMPATIBLE CHANGE) files included in a bundle via [http://eclipse.org/tycho/sitedocs/tycho-packaging-plugin/package-plugin-mojo.html#additionalFileSets additionalFileSets] now take precedence over <tt>bin.includes</tt> if conflicting ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=419849 bug 419849])

+

+

=== Other ===

+

+

<p><ul>

+

<li> <tt>tycho-version-plugin:set-version</tt> now also updates versions of exported packages, when the packages have the same version as the bundle version without qualifier.</li>

* (INCOMPATIBLE CHANGE) By default, any uncommitted local changes will now fail the build to ensure reproducibility.

+

* Configuration option <tt>jgit.dirtyWorkingTree</tt> allows to control behaviour in case of uncommitted changes detected for a module:

+

** <tt>error</tt> (default): fail the build if <tt>git status</tt> is not clean. This is useful for production builds to make sure the commit timestamp build qualifier used is really reproducible

+

** <tt>warning</tt>: 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.

+

** <tt>ignore</tt>: do not check whether <tt>git status</tt> is clean and use the timestamp of the last git commit as build qualifier regardless of uncommitted changes done on top. This can be used in case jgit should report a false positive dirty working tree or in case you want to restore pre-0.19.0 behaviour.

Contents

New and Noteworthy

Target Platform & Dependency Resolution

(INCOMPATIBLE CHANGE) The syntax for specifying profile properties during dependency resolution was changed to the normal <key>value</key> syntax. See bug 412283 for an example.

(INCOMPATIBLE CHANGE) system-scoped pom dependencies will now be ignored if used with pomDependencies=consider (bug 415774). This corner case was supported only half-way anyway. If you absolutely have to use local-only jars with pomDependencies=consider, use e.g. mvn install:install-file instead which will allow to reference them as normal (compile-scoped) pom dependencies without a hardcoded filesystem path.

Bundle-ClassPath: external:... MANIFEST entries in referenced bundles no longer fail the build, but will be ignored with a warning now (bug 370958)

The logging of download problems for artifacts from p2 repositories has been significantly improved.

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 "example.product.id", test bundle and tycho surefire test harness bundles using the p2 director, use the following pom.xml snippet in the test module:

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 site docs for details.

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

(INCOMPATIBLE CHANGE) By default, any uncommitted local changes will now fail the build to ensure reproducibility.

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 regardless of uncommitted changes done on top. This can be used in case jgit should report a false positive dirty working tree or in case you want to restore pre-0.19.0 behaviour.