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

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

−

==== Complier Plugin ====

+

==== Compiler Plugin ====

* (INCOMPATIBLE CHANGE) <tt>eclipse-plugin</tt> and <tt>eclipse-test-plugin</tt> modules which neither have and explicit [http://www.eclipse.org/tycho/sitedocs/tycho-compiler-plugin/compile-mojo.html compiler source/target level] configuration nor have an [http://wiki.eclipse.org/Tycho/Execution_Environments#Execution_environment_configuration execution environment] configuration are now compiled with a source & target level of 1.6 instead of 1.5. Modules with any explicit configuration, e.g. a <tt>Bundle-RequiredExecutionEnvironment</tt> header in the manifest, are not affected. If you are building for <tt>J2SE-1.5</tt> or even more restricted execution environments, it is recommended to set the new <tt>target-platform-configuration</tt> parameter <tt>&lt;executionEnvironmentDefault&gt;</tt> in your parent POM.

* (INCOMPATIBLE CHANGE) <tt>eclipse-plugin</tt> and <tt>eclipse-test-plugin</tt> modules which neither have and explicit [http://www.eclipse.org/tycho/sitedocs/tycho-compiler-plugin/compile-mojo.html compiler source/target level] configuration nor have an [http://wiki.eclipse.org/Tycho/Execution_Environments#Execution_environment_configuration execution environment] configuration are now compiled with a source & target level of 1.6 instead of 1.5. Modules with any explicit configuration, e.g. a <tt>Bundle-RequiredExecutionEnvironment</tt> header in the manifest, are not affected. If you are building for <tt>J2SE-1.5</tt> or even more restricted execution environments, it is recommended to set the new <tt>target-platform-configuration</tt> parameter <tt>&lt;executionEnvironmentDefault&gt;</tt> in your parent POM.

Contents

New and Noteworthy

Compiler Plugin

(INCOMPATIBLE CHANGE) eclipse-plugin and eclipse-test-plugin modules which neither have and explicit compiler source/target level configuration nor have an execution environment configuration are now compiled with a source & target level of 1.6 instead of 1.5. Modules with any explicit configuration, e.g. a Bundle-RequiredExecutionEnvironment header in the manifest, are not affected. If you are building for J2SE-1.5 or even more restricted execution environments, it is recommended to set the new target-platform-configuration parameter <executionEnvironmentDefault> in your parent POM.

The JDT compiler bundled with Tycho has been updated to Kepler M6.

The tycho-compiler-plugin has a new compilerArgs parameter that allows to specify arbitrary compiler arguments (see bug 400307)

The compilation bootclasspath can now be customized in toolchains.xml when using useJDK=BREE (bug 389856).

Target Platform & Dependency Resolution

It is now possible to specify multiple target files in target-platform-configuration. Note that these target files are resolved separately, i.e. they each need to resolve successfully when opened with the target editor in Eclipse. Also note that it is not possible to activate multiple target files in the Eclipse PDE (see bug 392652).

p2 repository and proxy authentication now works with maven-encrypted passwords (bug 386910 and bug 394023)

The Equinox and p2 versions bundled with Tycho has been updated to Kepler M6.

This includes an update to a new major version (4.1.3) of the bundled Apache httpclient library.

Test Execution

Source Features

(INCOMPATIBLE CHANGE) No longer rely on existence of magic folder sourceTemplateFeature/ when determining whether to generate a source feature

Label, description, branding plugin and other attributes are now taken over from the original feature by default. See bugs 374349, 375165 and 378424 for details. It's recommended to rely on feature.properties to set name and other text values in the original feature; then you can easily customize/override the generated source feature values by creating a sourceTemplateFeature/feature.properties file if required