Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

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

m
m
 
(11 intermediate revisions by 3 users not shown)
Line 3: Line 3:
 
   #versionNav{ position:absolute; top: 0px; right: 0px; border-color: transparent; background: transparent; }
 
   #versionNav{ position:absolute; top: 0px; right: 0px; border-color: transparent; background: transparent; }
 
</css>  
 
</css>  
<div id="versionNav" class="alert alert-small alert-warning">[[Tycho/Release Notes/1.1|&lt; Previous Version]] | Next Version &gt;</div>  
+
<div id="versionNav" class="alert alert-small alert-warning">[[Tycho/Release Notes/1.1|&lt; Previous Version]] | [[Tycho/Release Notes/1.3|Next Version &gt;]]</div>  
 
+
== SNAPSHOT builds ==
+
 
+
Tycho 1.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>1.2.0-SNAPSHOT</tt>.
+
 
+
<pre>
+
<pluginRepositories>
+
    <pluginRepository>
+
      <id>tycho-snapshots</id>
+
      <url>https://repo.eclipse.org/content/repositories/tycho-snapshots/</url>
+
    </pluginRepository>
+
</pluginRepositories>
+
</pre>
+
+
=== SNAPSHOT site docs ===
+
 
+
Refer to the [https://ci.eclipse.org/tycho/job/tycho-sitedocs/ws/target/staging/index.html latest SNAPSHOT site docs for Tycho] and [https://ci.eclipse.org/tycho/job/tycho.extras-sitedocs/ws/target/staging/index.html Tycho Extras].
+
 
+
  
 +
 
== New and Noteworthy ==
 
== New and Noteworthy ==
  
[https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&product=Tycho&query_format=advanced&target_milestone=1.2.0&order=bug_id&query_based_on= Complete list of bug fixes and enhancements in 1.2.0-SNAPSHOT]
+
[https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&product=Tycho&query_format=advanced&target_milestone=1.2.0&order=bug_id&query_based_on= Complete list of bug fixes and enhancements in 1.2.0]
  
 
=== Testing ===
 
=== Testing ===
  
* Support for JUnit 5 is here!
+
* Support for '''JUnit 5''' is here! ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=522475 bug 522475])
 
**  We ported [https://github.com/junit-team/junit5/tree/master/junit-platform-surefire-provider junit-platform-surefire-provider] to Tycho. As soon as a test bundle requires any of the <tt>org.junit.jupiter.api.*</tt> packages, the JUnit 5 surefire provider is used, no need for explicit configuration in the default case.
 
**  We ported [https://github.com/junit-team/junit5/tree/master/junit-platform-surefire-provider junit-platform-surefire-provider] to Tycho. As soon as a test bundle requires any of the <tt>org.junit.jupiter.api.*</tt> packages, the JUnit 5 surefire provider is used, no need for explicit configuration in the default case.
 
** We added <tt>junit-vintage-engine</tt> so you can mix and match JUnit 5 and JUnit 4 tests in the same test bundle. This should ease gradual migration to JUnit 5
 
** We added <tt>junit-vintage-engine</tt> so you can mix and match JUnit 5 and JUnit 4 tests in the same test bundle. This should ease gradual migration to JUnit 5
** You can exclude or include test based on JUnit 5 tags, see the [http://git.eclipse.org/c/gerrit/tycho/org.eclipse.tycho.git/tree/tycho-its/projects/surefire.junit5/bundle.test/pom.xml#n31 JUnit 5 example test bundle] used by the integration tests
+
** You can exclude or include test based on JUnit 5 tags, see the [http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/tree/tycho-its/projects/surefire.junit5/bundle.test/pom.xml JUnit 5 example test bundle] used by the integration tests or the [https://wiki.eclipse.org/Tycho/How_Tos/JUnit5 JUnit5 How To]
 +
 
 +
== p2 and Dependency resolution ==
 +
 
 +
* Move to Equinox p2 Photon RC1 ( {{bug|534916}} )
 +
** This adds sha-256 signatures to p2 metadata for downloadable artifacts
 +
** Publish OSGi capabilites as p2 requires/provides and take them into account during dependency resolution.
 +
** The [[../../Execution_Environments|execution environment]] (EE) is now published as a requirement and taken into account during dependency resolution.
 +
* Default [[../../Execution_Environments|execution environment]], used when no better source in the module is found to decide it, is now <tt>JavaSE-9</tt>.
 +
* Support for building bundles requiring <tt>JavaSE-10</tt> has been added ( {{bug|532233}} )
 +
* Installable Units representing the execution environment (e.g. <tt>a.jre.javase</tt> version <tt>10.0.0</tt> representing <tt>JavaSE-10</tt>) are now explicitly published in projects of packaging type <tt>eclipse-repository</tt> (as opposed to implicitly when publishing a product). The default execution environment published is <tt>JavaSE-10</tt>, but this is [https://ci.eclipse.org/tycho/job/tycho-sitedocs/ws/target/staging/tycho-p2/tycho-p2-publisher-plugin/publish-osgi-ee-mojo.html configurable].
 +
 
  
 
[[Category:Tycho|Release Notes/1.2]]
 
[[Category:Tycho|Release Notes/1.2]]

Latest revision as of 04:04, 3 September 2018


New and Noteworthy

Complete list of bug fixes and enhancements in 1.2.0

Testing

  • Support for JUnit 5 is here! (bug 522475)
    • We ported junit-platform-surefire-provider to Tycho. As soon as a test bundle requires any of the org.junit.jupiter.api.* packages, the JUnit 5 surefire provider is used, no need for explicit configuration in the default case.
    • We added junit-vintage-engine so you can mix and match JUnit 5 and JUnit 4 tests in the same test bundle. This should ease gradual migration to JUnit 5
    • You can exclude or include test based on JUnit 5 tags, see the JUnit 5 example test bundle used by the integration tests or the JUnit5 How To

p2 and Dependency resolution

  • Move to Equinox p2 Photon RC1 ( bug 534916 )
    • This adds sha-256 signatures to p2 metadata for downloadable artifacts
    • Publish OSGi capabilites as p2 requires/provides and take them into account during dependency resolution.
    • The execution environment (EE) is now published as a requirement and taken into account during dependency resolution.
  • Default execution environment, used when no better source in the module is found to decide it, is now JavaSE-9.
  • Support for building bundles requiring JavaSE-10 has been added ( bug 532233 )
  • Installable Units representing the execution environment (e.g. a.jre.javase version 10.0.0 representing JavaSE-10) are now explicitly published in projects of packaging type eclipse-repository (as opposed to implicitly when publishing a product). The default execution environment published is JavaSE-10, but this is configurable.

Back to the top