View source for Tycho/Release Notes/2.2

<css>
  #main-page-content{ position:relative; }
  #versionNav{ position:absolute; top: 0px; right: 0px; border-color: transparent; background: transparent; }
</css>
<div id="versionNav" class="alert alert-small alert-warning">[[Tycho/Release Notes/2.1|&lt; Previous Version]] | [[Tycho/Release Notes/2.3|Next Version &gt;]]</div>

<!--

== SNAPSHOT builds ==

Tycho 2.2.0-SNAPSHOT is currently in development. To try out the most recent snapshot build, simply add the following snippet to your (parent) pom.xml or settings.xml, and set the property for the Tycho version (e.g. <tt>tycho-version</tt>) to <tt>2.2.0-SNAPSHOT</tt>.
 
<source lang="xml">
<pluginRepositories>
    <pluginRepository>
      <id>tycho-snapshots</id>
      <url>https://repo.eclipse.org/content/repositories/tycho-snapshots/</url>
    </pluginRepository>
</pluginRepositories>
</source>

=== SNAPSHOT site docs ===
 
Refer to the [https://ci.eclipse.org/tycho/job/tycho-sitedocs/lastSuccessfulBuild/artifact/target/staging/index.html latest SNAPSHOT site docs for Tycho].

== Staging build ==

Tycho 2.2.0 is currently staged for release. To try out the release candidate, simply add the following snippet to your (parent) pom.xml or settings.xml, and set the property for the Tycho version (e.g. <tt>tycho-version</tt>) to <tt>2.1.0</tt>.
 
<source lang="xml">
<pluginRepositories>
  <pluginRepository>
    <id>tycho-staged</id>
    <url>https://oss.sonatype.org/content/repositories/orgeclipsetycho-1064/</url>
  </pluginRepository>
</pluginRepositories>
</source>
-->

[[Category:Tycho|Release Notes/2.2]]

== New and Noteworthy ==

[https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&product=Tycho&query_format=advanced&target_milestone=2.2.0&order=bug_id&query_based_on= Complete list of bug fixes and enhancements in 2.2.0]<css>
  #main-page-content{ position:relative; }
  #versionNav{ position:absolute; top: 0px; right: 0px; border-color: transparent; background: transparent; }
</css>

=== Support for m2e PDE Maven target locations ===

{{bug|568729}}, {{bug|569481}} m2e includes a new feature that allows the usage of regular maven artifacts to be used in PDE target platforms. Support for this new location type was also added to tycho, you could read more about this new feature in the following [https://xn--lubisoft-0za.gmbh/en/articles/using-maven-artifacts-in-pde-rcp-and-tycho-builds/ article].

=== Allow parallel dependency resolving ===

{{bug|568446}} When using [https://cwiki.apache.org/confluence/display/MAVEN/Parallel+builds+in+Maven+3 parallel builds] the initial dependency resolution is now also executed in parallel.

=== Delay download of p2 artifacts for non-plugin modules ===

{{bug|567760}} Tycho now stops downloading p2 artifacts from remote sources too early and relies mostly on p2 metadata to compute target platform and build order without downloading the artifacts. Downloads are then instead delayed to when the artifact files are really necessary (to compute compilation build path, to generate a p2 repository...). As a result performance will be improved as less artifacts may be downloaded, and some steps like `mvn clean` or `mvn validate` can avoid downloading artifacts to process, and the most probable build failures will be reported faster.

Note that this is specifically visible for <tt>eclipse-feature</tt> and <tt>eclipse-repository</tt> modules; other module types like <tt>eclipse-plugin</tt> or <tt>eclipse-test-plugin</tt> do still require to downlaod artifacts early to create the build path. Further improvements remain possible on that topic.

=== Tycho Source Feature Generation moved from tycho extras to tycho core ===

{{bug|568359}} Historically the tycho-source-feature-plugin was located in tycho extras but could be confusing because they often are used in conjunction with to each other because a source-bundle is hardly useful without corresponding source-feature. With the merge of tycho-core and tycho-extras these separation becomes even more obsolete.

From now on, the tycho-source-plugin also includes the tycho-source-feature-plugin, the old one is deprecated and will be removed in the next major release.

Migration is rather simple, just add a new execution to the tycho-source-plugin
<source lang="xml">
<plugin>
	<groupId>org.eclipse.tycho</groupId>
	<artifactId>tycho-source-plugin</artifactId>
	<version>${tycho-version}</version>
	<executions>
	    <execution>
		<id>plugin-source</id>
		<goals>
		    <goal>plugin-source</goal>
		</goals>
	    </execution>
	     <execution>
		<id>feature-source</id>
		<goals>
		    <goal>feature-source</goal>
		</goals>
		<configuration>
		<!-- put your configuration here -->
		</configuration>
	    </execution>
	</executions>
</plugin>
</source>

Beside this, the new mojo does support one additional configuration option 'missingSourcesAction' that can have one of the following two values:
* FAIL: this is like the old mojo works, any missing source bundle that is not excluded will fail the build
* WARN: this is the default, a warning will be omitted listing all missing plugins/features that are not excluded

=== Support for consuming maven artifacts made of zipped P2 update sites ===

{{bug|398238}} Tycho now supports in target files and in <repository> elements URLs of the form mvn:groupId:artifactId:version[:packaging[:classifier]] to be used for a repository.

For example
 <repository>
  <id>activiti</id>
  <layout>p2</layout>
  <url>mvn:org.activiti.designer:org.activiti.designer.updatesite:5.11.1:zip</url>
 </repository>

=== Support for excluding files in build.properties ===

{{bug|568623}} Tycho now supports in build properties files to exclude files in library.

For example
 output.mycodelib.jar = bin/
 bin.includes = META-INF/,\
               mycodelib.jar
 
 source.mycodelib.jar = src/
 exclude.mycodelib.jar = **/*.txt