* (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) 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]). This 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 aloow to reference them as normal compile-scoped pom dependencies.

SNAPSHOT site docs

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 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 aloow to reference them as normal compile-scoped pom dependencies.

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 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)

Other

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.