Skip to main content
Jump to: navigation, search

Difference between revisions of "Tycho/Release Notes/0.23"

m
Line 28: Line 28:
 
=== Compiler ===
 
=== Compiler ===
  
* the JDT compiler shipped with Tycho has been updated to Mars M6 ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=461101 bug 461101]).
+
* the JDT compiler shipped with Tycho has been updated to Mars M7 ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=461101 bug 461101]).
  
 
=== Packaging Type ===
 
=== Packaging Type ===
Line 41: Line 41:
  
 
* (INCOMPATIBLE CHANGE) The tycho-surefire property <tt>testSuite</tt> had been removed. If you are building a multi-bundle project and had set the <tt>testSuite</tt> and <tt>testClass</tt> property on the CLI or in a parent pom, you have to set the property <tt>failIfNoTests</tt> to <tt>false</tt>. If you had specified <tt>testSuite</tt> and <tt>testClass</tt> in the pom file of the plugin the <tt>testsClass</tt> belongs to, you just have to remove the <tt>testSuite</tt> property ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=453526 <strike>bug 453526</strike>]).
 
* (INCOMPATIBLE CHANGE) The tycho-surefire property <tt>testSuite</tt> had been removed. If you are building a multi-bundle project and had set the <tt>testSuite</tt> and <tt>testClass</tt> property on the CLI or in a parent pom, you have to set the property <tt>failIfNoTests</tt> to <tt>false</tt>. If you had specified <tt>testSuite</tt> and <tt>testClass</tt> in the pom file of the plugin the <tt>testsClass</tt> belongs to, you just have to remove the <tt>testSuite</tt> property ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=453526 <strike>bug 453526</strike>]).
 +
 +
=== Other ===
 +
 +
*  The embedded OSGi runtime used by Tycho during build has been updated to use Equinox and p2 from the Mars M7 milestone ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=466320 bug 466320]).
  
 
=== Additional Tools ===
 
=== Additional Tools ===

Revision as of 04:08, 18 May 2015

< Previous Version | Next Version >

SNAPSHOT builds

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

<pluginRepositories>
   <pluginRepository>
     <id>tycho-snapshots</id>
     <url>https://repo.eclipse.org/content/repositories/tycho-snapshots/</url>
   </pluginRepository>
</pluginRepositories>

SNAPSHOT site docs

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

New and Noteworthy

Complete list of bug fixes and enhancements in 0.23.0

Compiler

  • the JDT compiler shipped with Tycho has been updated to Mars M7 (bug 461101).

Packaging Type

Packaging

  • You can now use <iu> elements in an eclipse-repository's category.xml to include and/or categorize arbitrary artifacts in a p2 repository (bug 371983). See Tycho/category.xml for details.

Test Execution

  • (INCOMPATIBLE CHANGE) The tycho-surefire property testSuite had been removed. If you are building a multi-bundle project and had set the testSuite and testClass property on the CLI or in a parent pom, you have to set the property failIfNoTests to false. If you had specified testSuite and testClass in the pom file of the plugin the testsClass belongs to, you just have to remove the testSuite property (bug 453526).

Other

  • The embedded OSGi runtime used by Tycho during build has been updated to use Equinox and p2 from the Mars M7 milestone (bug 466320).

Additional Tools

  • The tycho-document-bundle-plugin now allows to specify includes and excludes for the packages to be documented (bug 459214)
  • It is now possible to use a custom doclet in the tycho-document-bundle-plugin (bug 453602). The doclet parameter will be passed to javadoc as -doclet. The docletArtifacts are resolved (including the transitive depenencies) and passed to javadoc as -docletpath. Example configuration:
     <configuration>
        <javadocOptions>
           <ignoreError>false</ignoreError>
           <doclet>foo.bar.MyDoclet</doclet>
           <docletArtifacts>
              <docletArtifact>
                 <groupId>foo.bar</groupId>
                 <artifactId>foo.bar.mydocletartifact</artifactId>
                 <version>1.0</version>
              </docletArtifact>
           </docletArtifacts>
        </javadocOptions>
     </configuration>
    

Back to the top