blob: 06897af4c346b34f38a82dcf7e1769bbecbd6f3a [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Xtext - Language Engineering Framework</title>
<description>Xtext is a framework for development of programming languages and domain specific languages. It covers all aspects of a complete language infrastructure, from parsers, over linker, compiler or interpreter to fully-blown top-notch Eclipse IDE integration. It comes with great defaults for all these aspects which at the same time can be easily tailored to your individual needs.
</description>
<link>http://xtext.org/Xtext/</link>
<atom:link href="http://xtext.org/Xtext/feed.xml" rel="self" type="application/rss+xml"/>
<pubDate>Tue, 02 Jun 2020 06:29:54 +0000</pubDate>
<lastBuildDate>Tue, 02 Jun 2020 06:29:54 +0000</lastBuildDate>
<generator>Jekyll v2.5.3</generator>
<item>
<title>Xtext 2.21.0 Release Notes</title>
<description>&lt;p&gt;Xtext 2.21 is mainly a maintenance release with a focus on internal improvements to enable more people to contribute and only a few new features. The internal usage of Xtend was reduced where it is not beneficial. This improves build performance and lowers the barrier for new contributors. Also all the tests that were failing on Windows only were adapted, such that developing Xtext on Windows machines is now more satisfying.&lt;/p&gt;
&lt;h2 id=&quot;license-change&quot;&gt;License Change&lt;/h2&gt;
&lt;p&gt;In compliance with general requirements by the Eclipse Foundation the license for Xtext &amp;amp; Xtend has been changed to &lt;a href=&quot;https://www.eclipse.org/legal/epl-2.0/&quot;&gt;EPL 2.0&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;documentation&quot;&gt;Documentation&lt;/h2&gt;
&lt;p&gt;The &lt;a href=&quot;https://www.eclipse.org/Xtext/community.html&quot;&gt;Xtext community website&lt;/a&gt; has been updated to list all the cool projects people are building around Xtext/Xtend.&lt;br /&gt;
The list is not yet complete, so feel free to contact us if you are also interested in listing your project there.&lt;/p&gt;
&lt;p&gt;The documentation about the &lt;a href=&quot;https://github.com/eclipse/xtext/blob/master/dev-doc/MaintenanceTasks.md&quot;&gt;release process&lt;/a&gt; was improved to enable more people to contribute to this process.&lt;/p&gt;
&lt;h2 id=&quot;eclipse-integration&quot;&gt;Eclipse Integration&lt;/h2&gt;
&lt;h3 id=&quot;skip-create-markers-in-target-folders&quot;&gt;Skip create markers in target folders&lt;/h3&gt;
&lt;p&gt;Creation of markers in target folders is disabled. This avoids confusing error markers and improves performance at the same time.&lt;/p&gt;
&lt;h3 id=&quot;avoid-generation-of-dependency-to-xpandold-generator&quot;&gt;Avoid generation of dependency to Xpand/old generator&lt;/h3&gt;
&lt;p&gt;The wizard to generate projects for existing ecore models does not create a dependency to deprecated Xpand/old generator any more.&lt;/p&gt;
&lt;h2 id=&quot;xtext-maven-plugin&quot;&gt;xtext-maven-plugin&lt;/h2&gt;
&lt;h3 id=&quot;testgenerate-goal&quot;&gt;testGenerate Goal&lt;/h3&gt;
&lt;p&gt;The Maven plugin has now two goals, &lt;code&gt;generate&lt;/code&gt; and &lt;code&gt;testGenerate&lt;/code&gt;. The new &lt;code&gt;testGenerate&lt;/code&gt; goal runs during the &lt;code&gt;generate-test-sources&lt;/code&gt; phase and uses the test classpath of the Maven project.&lt;/p&gt;
&lt;h2 id=&quot;lsp&quot;&gt;LSP&lt;/h2&gt;
&lt;h3 id=&quot;multiple-root-folders-per-workspace&quot;&gt;Multiple root folders per workspace&lt;/h3&gt;
&lt;p&gt;Xtext based languages now allow a workspace to be composed of multiple root folders.&lt;/p&gt;
&lt;h2 id=&quot;upgrades&quot;&gt;Upgrades&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;MWE(2) was updated to 2.11.2 / 1.5.2.&lt;/li&gt;
&lt;li&gt;Xtext 2.21 now requires EMF 2.20 as minimal required version.&lt;/li&gt;
&lt;li&gt;LSP4J is now on version 0.9.0 / Language Server Protocol version 3.15.&lt;/li&gt;
&lt;li&gt;Maven Tycho was updated to version 1.6.0.&lt;/li&gt;
&lt;li&gt;JUnit was updated to version 5.6.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;deprecations&quot;&gt;Deprecations&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;In &lt;code&gt;org.eclipse.xtext.ide&lt;/code&gt; many of the LSP Services were changed in the protocol to use service specific parameters instead of &lt;code&gt;TextDocumentPositionParams&lt;/code&gt;. We adapted the services to use the new parameter classes and marked the old ones as deprecated and to be removed with Xtext 2.22. If you have custom subclasses of the affected services please adapt your implementations. This also holds true for deprecations in lsp services that we marked as deprecated in earlier releases.&lt;/li&gt;
&lt;li&gt;We again encourage you to get rid of the old generator as we might have to remove it in 2020-06 / Xtext 2.22 - see/join &lt;a href=&quot;https://github.com/eclipse/xtext/issues/1669&quot;&gt;Xtext Issue #1669&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;credits&quot;&gt;Credits&lt;/h2&gt;
&lt;p&gt;The Xtext project is thankful for the dedication of each committer and contributor. This release has been made possible by the following persons (in order of the number of contributed commits to this release to &lt;a href=&quot;https://github.com/eclipse/xtext#repositories&quot;&gt;all repositories&lt;/a&gt; except &lt;a href=&quot;https://github.com/eclipse/xtext-xtend&quot;&gt;xtext-xtend&lt;/a&gt;):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Christian Dietrich (itemis)&lt;/li&gt;
&lt;li&gt;Karsten Thoms (Karakun)&lt;/li&gt;
&lt;li&gt;Sebastian Zarnekow (independent)&lt;/li&gt;
&lt;li&gt;Nico Prediger (itemis)&lt;/li&gt;
&lt;li&gt;Tamas Miklossy (itemis)&lt;/li&gt;
&lt;li&gt;Arne Deutsch (itemis)&lt;/li&gt;
&lt;li&gt;Marcus Mews (NumberFour)&lt;/li&gt;
&lt;li&gt;Lorenzo Bettini (Università degli Studi di Firenze)&lt;/li&gt;
&lt;li&gt;Sven Efftinge (TypeFox)&lt;/li&gt;
&lt;li&gt;Jan Rosczak (Hapag-Lloyd)&lt;/li&gt;
&lt;li&gt;Jan Koehnlein (TypeFox)&lt;/li&gt;
&lt;li&gt;Robert Lewis &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Ryan Dunn &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Mathias Rieder (Bachmann)&lt;/li&gt;
&lt;li&gt;Hannes Niederhausen (itemis) &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;David Medina (Sigasi) &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;fixed-issues&quot;&gt;Fixed Issues&lt;/h2&gt;
&lt;p&gt;As in every release cycle we were eagerly hunting down bugs, and reviewed and integrated plenty of contributions. Almost 60 issues and 320 pull requests have made it into this release. For further details please refer to the following lists:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Aissue+milestone%3ARelease_2.21+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Fixed GitHub issues&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Apr+milestone%3ARelease_2.21+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Closed Pull Requests&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&amp;amp;bug_status=VERIFIED&amp;amp;bug_status=CLOSED&amp;amp;classification=Modeling&amp;amp;classification=Tools&amp;amp;columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ckeywords&amp;amp;f0=OP&amp;amp;f1=OP&amp;amp;f3=CP&amp;amp;f4=CP&amp;amp;known_name=Xtext%202.21&amp;amp;list_id=16618269&amp;amp;product=TMF&amp;amp;product=Xtend&amp;amp;query_based_on=Xtext%202.21&amp;amp;query_format=advanced&amp;amp;status_whiteboard=v2.21&amp;amp;status_whiteboard_type=allwordssubstr&quot;&gt;Fixed Eclipse Bugzilla tickets&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description>
<pubDate>Tue, 03 Mar 2020 00:00:00 +0000</pubDate>
<link>http://xtext.org/Xtext/releasenotes/2020/03/03/version-2-21-0.html</link>
<guid isPermaLink="true">http://xtext.org/Xtext/releasenotes/2020/03/03/version-2-21-0.html</guid>
<category>releasenotes</category>
</item>
<item>
<title>Xtext 2.20.0 Release Notes</title>
<description>&lt;p&gt;Xtext 2.20.0 is mainly a maintenance release.&lt;/p&gt;
&lt;h2 id=&quot;eclipse-integration&quot;&gt;Eclipse Integration&lt;/h2&gt;
&lt;h3 id=&quot;egit-minimal-version&quot;&gt;EGit minimal version&lt;/h3&gt;
&lt;p&gt;Xtext requires to use EGit 4.1 or newer now. We have removed a workaround that prevented an endless build loop caused by EGit &lt;a href=&quot;https://bugs.eclipse.org/bugs/show_bug.cgi?id=474003&quot;&gt;Bug#474003&lt;/a&gt;. Since we expect that no clients are still using Xtext &amp;gt;= 2.20 together with the ancient EGit version, we felt safe to finally remove this workaround.&lt;/p&gt;
&lt;h3 id=&quot;new-project-wizard--new-file-wizard-improvements&quot;&gt;New Project Wizard / New File Wizard improvements&lt;/h3&gt;
&lt;p&gt;The &lt;code&gt;New Project Wizard&lt;/code&gt; / &lt;code&gt;New File Wizard&lt;/code&gt; generator fragments have been extended by the &lt;code&gt;generateToolbarButton&lt;/code&gt; option. Setting this option to &lt;code&gt;true&lt;/code&gt; adds new project wizard / new file wizard buttons to the toolbar. Furthermore, the New Project Wizard templates provide an API to&lt;br /&gt;
register images that can be used in the template descriptions. All these wizard improvements are demonstrated by the Statemachine example shipped by the Xtext framework.&lt;/p&gt;
&lt;h2 id=&quot;xtext-web&quot;&gt;Xtext-Web&lt;/h2&gt;
&lt;p&gt;The &lt;code&gt;Xtext-Web Entities Example&lt;/code&gt; provides improved validator and formatter capabilities, such as validating the entity, property and operation names, validating the uniquness of the property/operation definitions as well as properly formatting the defined packages, entities, properties and operations elements.&lt;/p&gt;
&lt;h2 id=&quot;upgrades&quot;&gt;Upgrades&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The Eclipse Modeling Workflow Engine (MWE2) was updated to version 2.11.1.&lt;/li&gt;
&lt;li&gt;LSP4J is now on version 0.8.1.&lt;/li&gt;
&lt;li&gt;Maven Tycho was updated to version 1.5.1.&lt;/li&gt;
&lt;li&gt;Gradle to version 5.6.x (Should also work with Gradle 6.0.x which we will ship with Xtext 2.21).&lt;/li&gt;
&lt;li&gt;grgit Gradle Plugin 4.0.0&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;xtend&quot;&gt;Xtend&lt;/h2&gt;
&lt;p&gt;A word on Xtend. Back in 2013 Xtend was the “Java 10 of today” even before Java 8 was out. Meanwhile Java Release cadence has speeded up and many of Xtends features can be achieved with pure Java, too. There is still some areas where Xtend is particularly advanced like Code generation, Unit tests and lambda heavy APIs like JvmModelInferrer and Formatter. For other tasks there is no need to use Xtend. Also the resources we have no longer allow us to keep the head start against Java. And learning Xtend still is a burden for new Xtext users. To reflect this changed situation we have decided to make Java the default in the wizard again (except e.g. the Generator and a few other APIs). You can still decide if you want Java or Xtend in the workflow.&lt;/p&gt;
&lt;h2 id=&quot;deprecations&quot;&gt;Deprecations&lt;/h2&gt;
&lt;h3 id=&quot;old-generator&quot;&gt;Old Generator&lt;/h3&gt;
&lt;p&gt;With Xtext 2.9 we changed the way Xtext languages are generated to a new generator infrastructure/workflow (&lt;code&gt;org.eclipse.xtext.xtext.generator&lt;/code&gt;). Until now we still kept the support for the old (Xpand based) workflows and generator (&lt;code&gt;org.eclipse.xtext.generator&lt;/code&gt;). We also allowed to use old generator fragments in new workflows through &lt;code&gt;org.eclipse.xtext.generator.adapter.FragmentAdapter&lt;/code&gt;. As we want to stop using old Xpand in Xtext we will drop this support in a future Xtext release. We strongly recommend you to migrate to the new workflow and to get rid of the usages of &lt;code&gt;FragmentAdapter&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id=&quot;xtend1-based-ixtext2ecorepostprocessor&quot;&gt;Xtend(1) based IXtext2EcorePostProcessor&lt;/h3&gt;
&lt;p&gt;Xtext has basically two methods to work with metamodels. The first on is to infer the metamodel from the Grammar. The second one is to maintain it manually and import it in Xtext. In the past we had actually a third option too: To hook into the inference with a &lt;code&gt;IXtext2EcorePostProcessor&lt;/code&gt; written in old Xtend(1). We plan to drop this feature in the future and recommend you to switch to a manually maintained metamodel.&lt;/p&gt;
&lt;h2 id=&quot;credits&quot;&gt;Credits&lt;/h2&gt;
&lt;p&gt;The Xtext project is thankful for the dedication of each committer and contributor. This release has been made possible by the following persons (in order of the number of contributed commits to this release to &lt;a href=&quot;https://github.com/eclipse/xtext#repositories&quot;&gt;all repositories&lt;/a&gt; except &lt;a href=&quot;https://github.com/eclipse/xtext-xtend&quot;&gt;xtext-xtend&lt;/a&gt;):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Christian Dietrich (itemis)&lt;/li&gt;
&lt;li&gt;Karsten Thoms (itemis)&lt;/li&gt;
&lt;li&gt;Sebastian Zarnekow (independent)&lt;/li&gt;
&lt;li&gt;Tamas Miklossy (itemis)&lt;/li&gt;
&lt;li&gt;D. Gabriel (Bachmann) &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Jan Köhnlein (TypeFox)&lt;/li&gt;
&lt;li&gt;Arne Deutsch (itemis)&lt;/li&gt;
&lt;li&gt;Mathias Rieder &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Elena Rogleva &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Mark Christiaens (Sigasi)&lt;/li&gt;
&lt;li&gt;Simeon Andreev (Advantest) &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Stéphane Galland (Université de Technologie de Belfort)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;fixed-issues&quot;&gt;Fixed Issues&lt;/h2&gt;
&lt;p&gt;As in every release cycle we were eagerly hunting down bugs, and reviewed and integrated plenty of contributions. Almost 60 issues and 320 pull requests have made it into this release. For further details please refer to the following lists:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Aissue+milestone%3ARelease_2.20+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Fixed GitHub issues&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Apr+milestone%3ARelease_2.20+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Closed Pull Requests&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&amp;amp;bug_status=VERIFIED&amp;amp;bug_status=CLOSED&amp;amp;classification=Modeling&amp;amp;classification=Tools&amp;amp;columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ckeywords&amp;amp;f0=OP&amp;amp;f1=OP&amp;amp;f3=CP&amp;amp;f4=CP&amp;amp;known_name=Xtext%202.20&amp;amp;list_id=16618269&amp;amp;product=TMF&amp;amp;product=Xtend&amp;amp;query_based_on=Xtext%202.20&amp;amp;query_format=advanced&amp;amp;status_whiteboard=v2.20&amp;amp;status_whiteboard_type=allwordssubstr&quot;&gt;Fixed Eclipse Bugzilla tickets&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description>
<pubDate>Tue, 03 Dec 2019 00:00:00 +0000</pubDate>
<link>http://xtext.org/Xtext/releasenotes/2019/12/03/version-2-20-0.html</link>
<guid isPermaLink="true">http://xtext.org/Xtext/releasenotes/2019/12/03/version-2-20-0.html</guid>
<category>releasenotes</category>
</item>
<item>
<title>Xtext 2.19.0 Release Notes</title>
<description>&lt;p&gt;Xtext 2.19.0 is mainly a maintenance release.&lt;/p&gt;
&lt;h2 id=&quot;lsp-integration&quot;&gt;LSP Integration&lt;/h2&gt;
&lt;p&gt;Xtext 2.19 now uses LSP4J version 0.8.0 / Language Server Protocol version 3.14.0. This allows you to consume Xtext Language Servers through WebSocket.&lt;/p&gt;
&lt;h2 id=&quot;classgraph&quot;&gt;Classgraph&lt;/h2&gt;
&lt;p&gt;We use Classgraph to scan the classpath. This allows us to provide Standlone Content Assist proposals (LSP/WEB) not only when the application runs with Java 8 but with Java 11, too.&lt;/p&gt;
&lt;h2 id=&quot;upgrades&quot;&gt;Upgrades&lt;/h2&gt;
&lt;p&gt;Xtext now uses Guava 27.1.0. The new version will be picked up automatically if you make use of the Xtext BOM or consume Xtext from its P2 repository.&lt;br /&gt;
The MWE(2) version was updated to 2.11.&lt;/p&gt;
&lt;h2 id=&quot;gradle&quot;&gt;Gradle&lt;/h2&gt;
&lt;p&gt;We made building Xtext projects and Xtext itself Gradle 6.0 ready and thus future-proof.&lt;/p&gt;
&lt;h2 id=&quot;maven-tycho&quot;&gt;Maven Tycho&lt;/h2&gt;
&lt;p&gt;For our integration of Eclipse Tycho based builds with Eclipse Orbit we now make use of the new Orbit Simrel Alias &lt;a href=&quot;https://download.eclipse.org/tools/orbit/downloads/2019-09&quot;&gt;https://download.eclipse.org/tools/orbit/downloads/2019-09&lt;/a&gt; instead of our own solution &lt;a href=&quot;https://download.eclipse.org/modeling/tmf/xtext/updates/orbit/2019-09&quot;&gt;https://download.eclipse.org/modeling/tmf/xtext/updates/orbit/2019-09&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;infrastructure&quot;&gt;Infrastructure&lt;/h2&gt;
&lt;p&gt;Xtend now is built on the new Kubernetes based CBI infrastructure &lt;a href=&quot;https://wiki.eclipse.org/CBI/Jenkins_Migration_FAQ&quot;&gt;JIRO&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;more-upgrades&quot;&gt;More Upgrades&lt;/h2&gt;
&lt;p&gt;Xtext always follows the latest releases of the software it relies on. The following software upgrades have been considered for this release:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Latest supported Eclipse Platform 4.13 (a.k.a. 2019-09)&lt;/li&gt;
&lt;li&gt;Eclipse MWE 2.11&lt;/li&gt;
&lt;li&gt;Guava 27.1&lt;/li&gt;
&lt;li&gt;LSP4J 0.8&lt;/li&gt;
&lt;li&gt;jquery 3.4.1&lt;/li&gt;
&lt;li&gt;node 10.16.0&lt;/li&gt;
&lt;li&gt;Maven Plugins:
&lt;ul&gt;
&lt;li&gt;maven-compiler-plugin 3.8.1&lt;/li&gt;
&lt;li&gt;maven-source-plugin 3.1.0&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Gradle 5.5&lt;/li&gt;
&lt;li&gt;Gradle Plugins:
&lt;ul&gt;
&lt;li&gt;com.github.johnrengelman.shadow 5.1.0&lt;/li&gt;
&lt;li&gt;io.spring.dependency-management 1.0.8.RELEASE&lt;/li&gt;
&lt;li&gt;de.esoco.gwt 1.0.9&lt;/li&gt;
&lt;li&gt;org.ajoberstar.grgit 3.1.1&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;deprecations&quot;&gt;Deprecations&lt;/h2&gt;
&lt;h3 id=&quot;generator-fragments&quot;&gt;Generator Fragments&lt;/h3&gt;
&lt;p&gt;The generator fragments&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;org.eclipse.xtext.generator.adapter.FragmentAdapter&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;org.eclipse.xtext.generator.parser.antlr.XtextAntlrGeneratorComparisonFragment&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;have been marked deprecated. They are in the already deprecated bundle &lt;code&gt;org.eclipse.xtext.generator&lt;/code&gt;. There is currently no replacement for this fragment in the new &lt;code&gt;org.eclipse.xtext.xtext.generator&lt;/code&gt; bundle.&lt;/p&gt;
&lt;h2 id=&quot;credits&quot;&gt;Credits&lt;/h2&gt;
&lt;p&gt;The Xtext project is thankful for the dedication of each committer and contributor. This release has been made possible by the following persons (in order of the number of contributed commits to this release to &lt;a href=&quot;https://github.com/eclipse/xtext#repositories&quot;&gt;all repositories&lt;/a&gt; except &lt;a href=&quot;https://github.com/eclipse/xtext-xtend&quot;&gt;xtext-xtend&lt;/a&gt;):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Christian Dietrich (itemis)&lt;/li&gt;
&lt;li&gt;Karsten Thoms (itemis)&lt;/li&gt;
&lt;li&gt;Nico Prediger (itemis)&lt;/li&gt;
&lt;li&gt;Sebastian Zarnekow (itemis)&lt;/li&gt;
&lt;li&gt;Tamas Miklossy (itemis)&lt;/li&gt;
&lt;li&gt;Lorenzo Addazi (Mälardalen University Sweden)&lt;/li&gt;
&lt;li&gt;Marcus Mews (NumberFour)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;fixed-issues&quot;&gt;Fixed Issues&lt;/h2&gt;
&lt;p&gt;As in every release cycle we were eagerly hunting down bugs, and reviewed and integrated plenty of contributions. 85 issues and 330 pull requests have made it into this release. For further details please refer to the following lists:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Aissue+milestone%3ARelease_2.19+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Fixed GitHub issues&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Apr+milestone%3ARelease_2.19+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Closed Pull Requests&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&amp;amp;bug_status=VERIFIED&amp;amp;bug_status=CLOSED&amp;amp;classification=Modeling&amp;amp;classification=Tools&amp;amp;columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ckeywords&amp;amp;f0=OP&amp;amp;f1=OP&amp;amp;f3=CP&amp;amp;f4=CP&amp;amp;known_name=Xtext%202.19&amp;amp;list_id=16618269&amp;amp;product=TMF&amp;amp;product=Xtend&amp;amp;query_based_on=Xtext%202.19&amp;amp;query_format=advanced&amp;amp;status_whiteboard=v2.19&amp;amp;status_whiteboard_type=allwordssubstr&quot;&gt;Fixed Eclipse Bugzilla tickets&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description>
<pubDate>Tue, 03 Sep 2019 00:00:00 +0000</pubDate>
<link>http://xtext.org/Xtext/releasenotes/2019/09/03/version-2-19-0.html</link>
<guid isPermaLink="true">http://xtext.org/Xtext/releasenotes/2019/09/03/version-2-19-0.html</guid>
<category>releasenotes</category>
</item>
<item>
<title>Xtext 2.18.0 Release Notes</title>
<description>&lt;p&gt;Xtext 2.18.0 is mainly a maintenance release.&lt;/p&gt;
&lt;h2 id=&quot;eclipse-integration&quot;&gt;Eclipse Integration&lt;/h2&gt;
&lt;h3 id=&quot;search-references-result-page-new-context-actions&quot;&gt;Search References Result Page: New Context Actions&lt;/h3&gt;
&lt;p&gt;The results of the &lt;em&gt;Search References&lt;/em&gt; action can now be copied to the clipboard. Further an action has been added to remove search results from the view. Both actions are available from the context menu and by common keyboard shortcuts.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_18_SearchReferencesResultActions.png&quot; alt=&quot;Search References Result Page: New Context Actions&quot; height=&quot;50%&quot; width=&quot;50%&quot; /&gt;&lt;/p&gt;
&lt;h3 id=&quot;new-quickfix-on-empty-keywords&quot;&gt;New Quickfix on Empty Keywords&lt;/h3&gt;
&lt;p&gt;Grammar rules with empty keyword statements (&lt;code&gt;&#39;&#39;&lt;/code&gt;) are raising errors already. Two new quickfixes have been added that can be used to resolve these errors:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Remove the empty keyword&lt;/li&gt;
&lt;li&gt;Set the keyword value from the declaring rule name&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;(&lt;a href=&quot;https://github.com/eclipse/xtext-eclipse/issues/994&quot;&gt;xtext-eclipse#994&lt;/a&gt;)&lt;/p&gt;
&lt;h3 id=&quot;fixed-potential-deadlock-on-startup&quot;&gt;Fixed Potential Deadlock on Startup&lt;/h3&gt;
&lt;p&gt;A deadlock may occur on startup of Eclipse. The builder infrastructure has been improved to avoid locking on loading its stored state. (&lt;a href=&quot;https://github.com/eclipse/xtext/issues/1460&quot;&gt;#1460&lt;/a&gt;)&lt;/p&gt;
&lt;h3 id=&quot;fixed-exceptions-for-closed-projects&quot;&gt;Fixed: Exceptions for Closed Projects&lt;/h3&gt;
&lt;p&gt;When projects are removed from the workspace the &lt;code&gt;ProjectOpenedOrClosedListener&lt;/code&gt; may caused exceptions that were logged to the error log. This situation has been fixed with &lt;a href=&quot;https://github.com/eclipse/xtext-eclipse/issues/1066&quot;&gt;xtext-eclipse#1066&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&quot;refactoring-support-improved-progress-reporting&quot;&gt;Refactoring Support: Improved Progress Reporting&lt;/h3&gt;
&lt;p&gt;The &lt;code&gt;ResourceRelocationProcessor&lt;/code&gt; did not forward the progress monitor to the change serializer, which prevented proper feedback and cancellation support during the application of a rename refactoring. The progress monitor is now forwarded. (&lt;a href=&quot;https://github.com/eclipse/xtext-eclipse/issues/1053&quot;&gt;xtext-eclipse#1053&lt;/a&gt;)&lt;/p&gt;
&lt;h3 id=&quot;refactoring-support-improved-memory-utilization&quot;&gt;Refactoring Support: Improved Memory Utilization&lt;/h3&gt;
&lt;p&gt;During rename or move refactorings a temporary resource set is created and populated. This resource set was kept in memory, leading to unnecessary memory consumption. Now the memory held by this temporary resource set is released properly. (&lt;a href=&quot;https://github.com/eclipse/xtext-eclipse/issues/1048&quot;&gt;xtext-eclipse#1048&lt;/a&gt;)&lt;/p&gt;
&lt;h2 id=&quot;lsp-integration&quot;&gt;LSP Integration&lt;/h2&gt;
&lt;h3 id=&quot;ilanguageserveraccess-provide-access-to-xtext-index&quot;&gt;&lt;code&gt;ILanguageServerAccess&lt;/code&gt;: Provide Access to Xtext Index&lt;/h3&gt;
&lt;p&gt;A new method &lt;code&gt;doReadIndex&lt;/code&gt; has been added to &lt;code&gt;ILanguageServerAccess&lt;/code&gt; to allow access to the &lt;code&gt;IResourceDescritions&lt;/code&gt; instance (a.k.a. the Xtext Index). This is useful for certain use cases for LS extension developers. (&lt;a href=&quot;https://github.com/eclipse/xtext-core/issues/1067&quot;&gt;xtext#1067&lt;/a&gt;)&lt;/p&gt;
&lt;h3 id=&quot;report-partial-results-of-cancelled-multi-project-builds&quot;&gt;Report Partial Results of Cancelled Multi-Project Builds&lt;/h3&gt;
&lt;p&gt;When a multi-project build is canceled (another &lt;code&gt;runWrite&lt;/code&gt; coming in from the &lt;code&gt;RequestManager&lt;/code&gt;), it could be that some projects have already been built. Even though their &lt;code&gt;ProjectManager&lt;/code&gt;s have been updated (e.g. their index state), their deltas were never returned, because the &lt;code&gt;BuildManager&lt;/code&gt; aggregated all results in a local variable. Build listeners were never be informed about these changes.&lt;/p&gt;
&lt;p&gt;The &lt;code&gt;BuildManager&lt;/code&gt; has been improved to report also partial results to listeners. (&lt;a href=&quot;https://github.com/eclipse/xtext-core/issues/1124&quot;&gt;xtext-core#1124&lt;/a&gt;)&lt;/p&gt;
&lt;h3 id=&quot;improved-handling-of-builds-cancellations-by-didchangewatchedfiles-notifications&quot;&gt;Improved Handling of Builds Cancellations by &lt;code&gt;didChangeWatchedFiles&lt;/code&gt; Notifications&lt;/h3&gt;
&lt;p&gt;When editing files in an auto-saving editor, &lt;code&gt;didChange&lt;/code&gt; notifications are usually followed by &lt;code&gt;didChangeWatchedFiles&lt;/code&gt; notifications. The latter cancel the build, but only look at their own changes to decide whether a new build should be issued. The changes from the prior &lt;code&gt;didChange&lt;/code&gt; queued on the &lt;code&gt;BuildManager&lt;/code&gt; were ignored.&lt;/p&gt;
&lt;p&gt;This issue has been improved by reprocessing URIs from cancelled builds in. (&lt;a href=&quot;https://github.com/eclipse/xtext-core/issues/1121&quot;&gt;xtext-core#1121&lt;/a&gt;)&lt;/p&gt;
&lt;h3 id=&quot;fixed-unexpected-occurrance-highlighting&quot;&gt;Fixed Unexpected Occurrance Highlighting&lt;/h3&gt;
&lt;p&gt;In certain situations occurrances were not highlighted properly. The highlighting service has been improved for that. See &lt;a href=&quot;https://github.com/eclipse/xtext-core/issues/1090&quot;&gt;xtext-core#1090&lt;/a&gt; for details.&lt;/p&gt;
&lt;h2 id=&quot;xtext-grammar--code-generator&quot;&gt;Xtext Grammar &amp;amp; Code Generator&lt;/h2&gt;
&lt;h3 id=&quot;fixed-illegal-whitespace-removal-in-merged-manifests&quot;&gt;Fixed: Illegal Whitespace Removal in Merged Manifests&lt;/h3&gt;
&lt;p&gt;When re-generating language implementations whitespace was illegally removed for required bundles with changed versions. (&lt;a href=&quot;https://github.com/eclipse/xtext-extras/issues/406&quot;&gt;xtext-extras#406&lt;/a&gt;)&lt;/p&gt;
&lt;h2 id=&quot;security&quot;&gt;Security&lt;/h2&gt;
&lt;p&gt;With &lt;a href=&quot;https://bugs.eclipse.org/bugs/show_bug.cgi?id=544852&quot;&gt;Bug#544852&lt;/a&gt; a theoretical security issue was reported (CVE-2019-10249). While building Xtext artifacts may be downloaded through HTTP instead of HTTPS. To avoid this, all build related resources have been revised and assured that all artifacts participating in the software build are only downloaded with HTTPS.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;p2 mirrors are disabled for builds using Eclipse Tycho. (&lt;a href=&quot;https://github.com/eclipse/xtext/issues/1427&quot;&gt;#1427&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;p2 repository URLs changed from HTTP to HTTPS. (&lt;a href=&quot;https://github.com/eclipse/xtext-xtend/issues/759&quot;&gt;xtext-xtend#759&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Maven repository URLs changed from HTTP to HTTPS. (&lt;a href=&quot;https://github.com/eclipse/xtext-maven/issues/74&quot;&gt;xtext-maven&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;upgrades&quot;&gt;Upgrades&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;LSP4J has been upgraded to its latest release 0.7.2.&lt;/li&gt;
&lt;li&gt;The Java Bytecode Manipultation library ASM has been upgraded to version 7.1.0. (&lt;a href=&quot;https://github.com/eclipse/xtext/issues/1440&quot;&gt;#1440&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Gradle based projects have been upgraded to use the Gradle Wrapper version 5.4.1.&lt;/li&gt;
&lt;li&gt;Eclipse Tycho has been upgraded to release 1.4.0. (&lt;a href=&quot;https://github.com/eclipse/xtext/issues/1422&quot;&gt;#1422&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;In Gradle builds usages of Spring’s &lt;code&gt;dependency-management-plugin&lt;/code&gt; have been upgraded to version 1.0.7.RELEASE. (&lt;a href=&quot;https://github.com/eclipse/xtext/issues/1420&quot;&gt;#1420&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;new-features-in-xtend&quot;&gt;New Features in Xtend&lt;/h2&gt;
&lt;p&gt;Xtend has learned try-with-resources and the ternary operator. See the &lt;a href=&quot;https://www.eclipse.org/xtend/releasenotes.html#/releasenotes/2019/06/04/version-2-18-0&quot;&gt;Xtend Releasenotes&lt;/a&gt; for details.&lt;/p&gt;
&lt;h2 id=&quot;credits&quot;&gt;Credits&lt;/h2&gt;
&lt;p&gt;The Xtext project is thankful for the dedication of each committer and contributor. This release has been made possible by the following persons (in order of the number of contributed commits to this release to &lt;a href=&quot;https://github.com/eclipse/xtext#repositories&quot;&gt;all repositories&lt;/a&gt; except &lt;a href=&quot;https://github.com/eclipse/xtext-xtend&quot;&gt;xtext-xtend&lt;/a&gt;):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Christian Dietrich (itemis)&lt;/li&gt;
&lt;li&gt;Karsten Thoms (itemis)&lt;/li&gt;
&lt;li&gt;Sebastian Zarnekow (itemis)&lt;/li&gt;
&lt;li&gt;Jan Koehnlein (TypeFox)&lt;/li&gt;
&lt;li&gt;Holger Schill (itemis)&lt;/li&gt;
&lt;li&gt;Arne Deutsch (itemis)&lt;/li&gt;
&lt;li&gt;Christian Schneider (TypeFox)&lt;/li&gt;
&lt;li&gt;Titouan Vervack (Sigasi)&lt;/li&gt;
&lt;li&gt;Max Leuthäuser (itemis) &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Akos Kitta (TypeFox)&lt;/li&gt;
&lt;li&gt;Lorenzo Addazi&lt;/li&gt;
&lt;li&gt;Lorenzo Bettini (Università degli Studi di Firenze)&lt;/li&gt;
&lt;li&gt;Tamas Miklossy (itemis)&lt;/li&gt;
&lt;li&gt;Dennis Huebner (TypeFox)&lt;/li&gt;
&lt;li&gt;RhiobeT &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Sergio Otero Lopez &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Eva Poell (itemis)&lt;/li&gt;
&lt;li&gt;Lieven Lemiengre (Sigasi)&lt;/li&gt;
&lt;li&gt;Mark Christiaens (Sigasi)&lt;/li&gt;
&lt;li&gt;Michael Budnick (all4net) &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Stéphane Galland (Université de Technologie de Belfort)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;fixed-issues&quot;&gt;Fixed Issues&lt;/h2&gt;
&lt;p&gt;As in every release cycle we were eagerly hunting down bugs, and reviewed and integrated plenty of contributions. Almost 100 issues and 300 pull requests have made it into this release. For further details please refer to the following lists:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Aissue+milestone%3ARelease_2.18+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Fixed GitHub issues&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Apr+milestone%3ARelease_2.18+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Closed Pull Requests&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&amp;amp;bug_status=VERIFIED&amp;amp;bug_status=CLOSED&amp;amp;classification=Modeling&amp;amp;classification=Tools&amp;amp;columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ckeywords&amp;amp;f0=OP&amp;amp;f1=OP&amp;amp;f3=CP&amp;amp;f4=CP&amp;amp;known_name=Xtext%202.18&amp;amp;list_id=16618269&amp;amp;product=TMF&amp;amp;product=Xtend&amp;amp;query_based_on=Xtext%202.18&amp;amp;query_format=advanced&amp;amp;status_whiteboard=v2.18&amp;amp;status_whiteboard_type=allwordssubstr&quot;&gt;Fixed Eclipse Bugzilla tickets&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description>
<pubDate>Tue, 04 Jun 2019 00:00:00 +0000</pubDate>
<link>http://xtext.org/Xtext/releasenotes/2019/06/04/version-2-18-0.html</link>
<guid isPermaLink="true">http://xtext.org/Xtext/releasenotes/2019/06/04/version-2-18-0.html</guid>
<category>releasenotes</category>
</item>
<item>
<title>Xtext 2.17.1 Release Notes</title>
<description>&lt;p&gt;This is a hotfix release. Here is the list of fixed issues:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;There was a &lt;a href=&quot;https://bugs.eclipse.org/bugs/show_bug.cgi?id=545343&quot;&gt;bug&lt;/a&gt; in the Xtext Builder that leads to non Xtext projects being built by Xtext.&lt;/li&gt;
&lt;li&gt;The &lt;a href=&quot;https://github.com/eclipse/xtext-core/issues/1059&quot;&gt;LSP4J&lt;/a&gt; version in Xtext 2.17.0 did not match the one in Eclipse 2019-03. Upgraded to LSP4J 0.7.0.&lt;/li&gt;
&lt;li&gt;The &lt;a href=&quot;https://github.com/eclipse/xtext-xtend/issues/750&quot;&gt;Xtend Batch Compiler&lt;/a&gt; preferred classes found on the classpath over local classes.&lt;/li&gt;
&lt;/ul&gt;
</description>
<pubDate>Wed, 03 Apr 2019 00:00:00 +0000</pubDate>
<link>http://xtext.org/Xtext/releasenotes/2019/04/03/version-2-17-1.html</link>
<guid isPermaLink="true">http://xtext.org/Xtext/releasenotes/2019/04/03/version-2-17-1.html</guid>
<category>releasenotes</category>
</item>
<item>
<title>Xtext 2.17.0 Release Notes</title>
<description>&lt;p&gt;This release focuses on the compatibility with Java 11 &amp;amp; Eclipse 2019-03, stability, performance and technical debt reduction.&lt;/p&gt;
&lt;h2 id=&quot;bom&quot;&gt;BOM&lt;/h2&gt;
&lt;p&gt;Xtext 2.17 introduces a new artifact, a &lt;a href=&quot;https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies&quot;&gt;Maven BOM (&lt;em&gt;bill of materials&lt;/em&gt;)&lt;/a&gt;. Basically it is an artifact with packaging type &lt;code&gt;pom&lt;/code&gt;, which defines dependencies by a &lt;code&gt;&amp;lt;dependencyManagement&amp;gt;&lt;/code&gt; section. A BOM is consumed by client projects also by &lt;code&gt;&amp;lt;dependencyManagement&amp;gt;&lt;/code&gt; and using the BOM artifact with scope &lt;code&gt;import&lt;/code&gt; there.&lt;/p&gt;
&lt;p&gt;The BOM declares all dependencies that are used by Xtext and has the coordinates&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;groupId&lt;/code&gt; : &lt;code&gt;org.eclipse.xtext&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;artifactId&lt;/code&gt; : &lt;code&gt;xtext-dev-bom&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The &lt;code&gt;xtext-dev-bom&lt;/code&gt; is used in Maven configurations as follows:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt; &amp;lt;dependencyManagement&amp;gt;
&amp;lt;dependencies&amp;gt;
&amp;lt;dependency&amp;gt;
&amp;lt;groupId&amp;gt;org.eclipse.xtext&amp;lt;/groupId&amp;gt;
&amp;lt;artifactId&amp;gt;xtext-dev-bom&amp;lt;/artifactId&amp;gt;
&amp;lt;version&amp;gt;${xtext.version}&amp;lt;/version&amp;gt;
&amp;lt;type&amp;gt;pom&amp;lt;/type&amp;gt;
&amp;lt;scope&amp;gt;import&amp;lt;/scope&amp;gt;
&amp;lt;/dependency&amp;gt;
&amp;lt;/dependencies&amp;gt;
&amp;lt;/dependencyManagement&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Any artifact declared by the BOM (e.g. Eclipse Core, EMF, MWE, Guava, LSP4J, JDT, ANTLR) can then be used without declaration of a version.&lt;/p&gt;
&lt;p&gt;With Gradle 5 support of &lt;a href=&quot;https://docs.gradle.org/5.0/userguide/managing_transitive_dependencies.html#sec:bom_import&quot;&gt;BOM managed dependency versions&lt;/a&gt; was introduced. The Xtext BOM can be consumed by Gradle projects with the &lt;code&gt;platform&lt;/code&gt; dependency:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt; dependencies {
compile platform(&quot;org.eclipse.xtext:xtext-dev-bom:${xtextVersion}&quot;)
}
&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&quot;java-11&quot;&gt;Java 11&lt;/h2&gt;
&lt;p&gt;Xtext and Xtend now fully support Java 11! With Xtext 2.16 it was already possible to run Xtext on a Java 11 VM, but it was not possible to use Java 11 also as the target Java version. Since this required Java 11 enabled versions of Eclipse JDT, Tycho and Gradle and not all were available and especially not tested with Xtext, we had to defer the full support to 2.17.&lt;/p&gt;
&lt;p&gt;Now with that latest and greatest versions of JDT, Tycho and Gradle integrated, there are no restrictions to use Java 11 in any of the configurations.&lt;/p&gt;
&lt;h2 id=&quot;customizable-exception-handling-of-validation-code&quot;&gt;Customizable Exception Handling of Validation Code&lt;/h2&gt;
&lt;p&gt;By default Xtext swallows &lt;code&gt;NullPointerException&lt;/code&gt; occuring during the execution of validators. While this behavior is desirable in most cases and users are not bothered with faulty validation or the likely case of NPEs caused by accessing unresolvable proxies, it may be desirable to report or rethrow these exceptions. To minimize the effort of customizing, the handling of exceptions is delegated to the new API method &lt;code&gt;AbstractDeclarativeValidator#handleExceptionDuringValidation(Throwable)&lt;/code&gt;. Clients may overroide this method to change the exception handling behavior in their validator classes. (&lt;a href=&quot;https://github.com/eclipse/xtext-core/issues/983&quot;&gt;to issue&lt;/a&gt;)&lt;/p&gt;
&lt;h2 id=&quot;guava-210-version-pinning&quot;&gt;Guava 21.0 Version Pinning&lt;/h2&gt;
&lt;p&gt;Xtext allowed a version range from 14.0 to 21.0 for the Guava library in the past. Effectively this range became invalid since API introduced with Guava 20.0 was used in Xbase. The open version range lead also to other surprises in the past.&lt;/p&gt;
&lt;p&gt;With Xtext 2.17 it was decided to pin the required version of the Guava library to 21.0 only. This affects all bundle manifests for plugin builds as well as Gradle &amp;amp; Maven builds through the introduced BOM (see above). Also the &lt;em&gt;New Project Wizard&lt;/em&gt; will respect this restriction for newly created projects. (&lt;a href=&quot;https://github.com/eclipse/xtext/issues/1391&quot;&gt;to issue&lt;/a&gt;)&lt;/p&gt;
&lt;h2 id=&quot;xtext-grammar-language&quot;&gt;Xtext Grammar Language&lt;/h2&gt;
&lt;h3 id=&quot;new-validation-first-rule-must-not-be-a-fragment&quot;&gt;New Validation: First Rule Must Not Be a Fragment&lt;/h3&gt;
&lt;p&gt;An Xtext grammar’s first rule must not start with a fragment rule. This is now checked by an additional validation rule. (&lt;a href=&quot;https://github.com/eclipse/xtext-core/pull/1041&quot;&gt;to issue&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_17_Xtext_First-rule-not-a-fragment.gif&quot; alt=&quot;Validation: first rule not a fragment&quot; height=&quot;50%&quot; width=&quot;50%&quot; /&gt;&lt;/p&gt;
&lt;h2 id=&quot;testing&quot;&gt;Testing&lt;/h2&gt;
&lt;h3 id=&quot;hyperlinking&quot;&gt;Hyperlinking&lt;/h3&gt;
&lt;p&gt;A new base class &lt;code&gt;AbstractHyperlinkingTest&lt;/code&gt; has been added to provide a convenient way to test hyperlinking navigation.&lt;/p&gt;
&lt;p&gt;All standard example projects have been updated to provide a test class (&lt;code&gt;&amp;lt;LangugageName&amp;gt;HyperlinkingTest.java&lt;/code&gt;) for demonstration. (&lt;a href=&quot;https://github.com/eclipse/xtext-eclipse/issues/949&quot;&gt;to issue&lt;/a&gt;)&lt;/p&gt;
&lt;h3 id=&quot;junit-5-support&quot;&gt;JUnit 5 Support&lt;/h3&gt;
&lt;p&gt;The package &lt;code&gt;org.eclipse.xtext.testing.extensions&lt;/code&gt; introduced with release 2.14 is now public API, thus users of Xtext JUnit 5 support will no longer receive restricted API usage warnings.&lt;/p&gt;
&lt;p&gt;The &lt;em&gt;New Project Wizard&lt;/em&gt; selects JUnit 5 as default.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_17_Xtext_JUnit5-default.png&quot; alt=&quot;JUnit 5 support as default&quot; height=&quot;50%&quot; width=&quot;50%&quot; /&gt;&lt;/p&gt;
&lt;h2 id=&quot;xtext-maven-plugin&quot;&gt;xtext-maven-plugin&lt;/h2&gt;
&lt;h3 id=&quot;output-configuration-name&quot;&gt;Output Configuration Name&lt;/h3&gt;
&lt;p&gt;It is now possible to configure set the &lt;code&gt;name&lt;/code&gt; attribute for non-default output configurations. (&lt;a href=&quot;https://github.com/eclipse/xtext-maven/issues/62&quot;&gt;to issue&lt;/a&gt;)&lt;/p&gt;
&lt;h3 id=&quot;upgrade-to-maven-3-api&quot;&gt;Upgrade to Maven 3 API&lt;/h3&gt;
&lt;p&gt;The &lt;code&gt;xtext-maven-plugin&lt;/code&gt; has been refactored to use the latest Maven 3 API. The most significant internal change is that all doclet based configurations have been changed to use Maven 3 annotation API.&lt;/p&gt;
&lt;h2 id=&quot;xtext-web&quot;&gt;xtext-web&lt;/h2&gt;
&lt;p&gt;The Xtext web support has been updated to the latest versions of the used libraries and editors. Particularly we upgraded to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;requirejs 2.3.6&lt;/li&gt;
&lt;li&gt;jquery 3.3.1-1&lt;/li&gt;
&lt;li&gt;ace 1.3.3&lt;/li&gt;
&lt;li&gt;codemirror 5.41.0&lt;/li&gt;
&lt;li&gt;Orion 17&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;upgrades&quot;&gt;Upgrades&lt;/h2&gt;
&lt;p&gt;Xtext builts on top of numerous technologies which frequently provide releases. An important task is therefore to keep up-to-date with the latest from the used technology stack. All upgrades affect Xtext in multiple ways:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;All internal usages for building Xtext use the upgraded versions&lt;/li&gt;
&lt;li&gt;The &lt;em&gt;New Project Wizard&lt;/em&gt; produces projects that make use of upgrades&lt;/li&gt;
&lt;li&gt;Our provided Oomph setup has been updated to reflect the latest changes&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;eclipse-2019-03&quot;&gt;Eclipse 2019-03&lt;/h3&gt;
&lt;p&gt;As member of the Eclipse Simultaneous Release Xtext is also built against the latest target platform 2019-03.&lt;/p&gt;
&lt;h3 id=&quot;gradle-521&quot;&gt;Gradle 5.2.1&lt;/h3&gt;
&lt;p&gt;We upgraded to Gradle 5.2.1. This version is used especially to support the introduced Maven BOM (see above) “natively” in Gradle configurations.&lt;/p&gt;
&lt;h3 id=&quot;tycho-130&quot;&gt;Tycho 1.3.0&lt;/h3&gt;
&lt;p&gt;Tycho 1.3.0 is required especially for full Java 11 support.&lt;/p&gt;
&lt;h3 id=&quot;mwe-210&quot;&gt;MWE 2.10&lt;/h3&gt;
&lt;p&gt;Xtext is now the latest release 2.10 of the Modeling Workflow Engine (MWE). The MWE project has been updated to use a recent Xtext version itself and supports now separate source folders for main sources and tests.&lt;/p&gt;
&lt;h3 id=&quot;eclipse-orbit&quot;&gt;Eclipse Orbit&lt;/h3&gt;
&lt;p&gt;Xtext uses the Orbit repository &lt;a href=&quot;https://download.eclipse.org/releases/2019-03/&quot;&gt;https://download.eclipse.org/releases/2019-03/&lt;/a&gt; for third party libraries. The location redirects to the latest repository recommended for the simultanous release.&lt;/p&gt;
&lt;h2 id=&quot;credits&quot;&gt;Credits&lt;/h2&gt;
&lt;p&gt;The Xtext project is thankful for the dedication of each committer and contributor. This release has been made possible by the following persons (in order of the number of contributed commits to this release to &lt;a href=&quot;https://github.com/eclipse/xtext#repositories&quot;&gt;all repositories&lt;/a&gt; except &lt;a href=&quot;https://github.com/eclipse/xtext-xtend&quot;&gt;xtext-xtend&lt;/a&gt;):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Christian Dietrich (itemis)&lt;/li&gt;
&lt;li&gt;Karsten Thoms (itemis)&lt;/li&gt;
&lt;li&gt;Sebastian Zarnekow (itemis)&lt;/li&gt;
&lt;li&gt;Tamas Miklossy (itemis)&lt;/li&gt;
&lt;li&gt;Holger Schill (itemis)&lt;/li&gt;
&lt;li&gt;Arne Deutsch (itemis)&lt;/li&gt;
&lt;li&gt;Prajwal Gowda (itemis) &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Anders Dahlberg (Ericsson) &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Eva Poell (itemis) &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Lorenzo Addazi &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Jan Rosczak &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Jelle Schuhmacher (Altran) &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Titouan Vervack (Sigasi)&lt;/li&gt;
&lt;li&gt;Jonathan Menzies &lt;img src=&quot;https://img.shields.io/badge/-first%20time%20contributor-green.svg&quot; alt=&quot;&quot; /&gt;&lt;/li&gt;
&lt;li&gt;Christian Schneider (TypeFox)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;fixed-issues&quot;&gt;Fixed Issues&lt;/h2&gt;
&lt;p&gt;As in every release cycle we were eagerly hunting down bugs, and reviewed and integrated plenty of contributions. Almost 80 issues and 240 pull requests have made it into this release. For further details please refer to the following lists:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Aissue+milestone%3ARelease_2.17+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Fixed GitHub issues&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Apr+milestone%3ARelease_2.17+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Closed Pull Requests&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&amp;amp;bug_status=VERIFIED&amp;amp;bug_status=CLOSED&amp;amp;classification=Modeling&amp;amp;classification=Tools&amp;amp;columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ckeywords&amp;amp;f0=OP&amp;amp;f1=OP&amp;amp;f3=CP&amp;amp;f4=CP&amp;amp;known_name=Xtext%202.17&amp;amp;list_id=16618269&amp;amp;product=TMF&amp;amp;product=Xtend&amp;amp;query_based_on=Xtext%202.17&amp;amp;query_format=advanced&amp;amp;status_whiteboard=v2.17&amp;amp;status_whiteboard_type=allwordssubstr&quot;&gt;Fixed Eclipse Bugzilla tickets&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description>
<pubDate>Tue, 05 Mar 2019 00:00:00 +0000</pubDate>
<link>http://xtext.org/Xtext/releasenotes/2019/03/05/version-2-17-0.html</link>
<guid isPermaLink="true">http://xtext.org/Xtext/releasenotes/2019/03/05/version-2-17-0.html</guid>
<category>releasenotes</category>
</item>
<item>
<title>Xtext 2.16.0 Release Notes</title>
<description>&lt;p&gt;This release focuses on stability, performance and the compatibility with Eclipse 2018-12.&lt;/p&gt;
&lt;h2 id=&quot;java-11-preparation&quot;&gt;Java 11 preparation&lt;/h2&gt;
&lt;p&gt;Java 11 has been released in September 2018 and &lt;a href=&quot;https://github.com/eclipse/xtext/issues/1182&quot;&gt;Xtext is in preparation&lt;/a&gt; for full support. Xtext relies on plenty of different components, each of which need to work with Java 11. So far, not all of these are available themselves. Other parties have released new versions that could not be integrated yet. As a result we had to reschedule Java 11 support for Xtext 2.17. However, some preparational work has already been included into Xtext 2.16:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ASM 7: The ASM bytecode analysis and manipulation framework has been upgraded to the latest version 7.0.&lt;/li&gt;
&lt;li&gt;Tycho 1.3: Tycho 1.3 is built against latest JDT, which is required to use Java 11. All projects and wizards have been upgraded to Tycho 1.3.&lt;/li&gt;
&lt;li&gt;Gradle: Xtext 2.16 builds against and uses Gradle 4.10.2 now.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;testing&quot;&gt;Testing&lt;/h2&gt;
&lt;h3 id=&quot;quickfix-testing-api&quot;&gt;Quickfix testing API&lt;/h3&gt;
&lt;p&gt;A new base class &lt;a href=&quot;https://github.com/eclipse/xtext-eclipse/blob/master/org.eclipse.xtext.ui.testing/src/org/eclipse/xtext/ui/testing/AbstractQuickfixTest.java&quot;&gt;&lt;code&gt;AbstractQuickfixTest&lt;/code&gt;&lt;/a&gt; allows the definition of test cases for quickfixes. Quickfixes can be tested by using the method&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-java&quot;&gt;public void testQuickfixesOn(CharSequence model, String issueCode, Quickfix... quickfixes)
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This method takes the original DSL text as its first argument. The second argument is the issue code of the problem that can be fixed by the quickfixes under test. Finally the third argument is an array of &lt;code&gt;Quickfix&lt;/code&gt; testing instances. A testable Quickfix defines a label, a description and the expected resulting DSL text.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-xtend&quot;&gt; @Data
protected static class Quickfix {
String label
String description
String result
}
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The Xtext example projects Domainmodel, Statemachine and Home Automation do include exemplary tests to demonstrate its usage. The Domainmodel example’s quickfix test looks like this:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-xtend&quot;&gt;class QuickfixTest extends AbstractQuickfixTest {
@Before
def void setup() {
}
@Test
def fix_invalid_entity_name() {
&#39;&#39;&#39;
entity blog {
}
&#39;&#39;&#39;.testQuickfixesOn(INVALID_TYPE_NAME, new Quickfix(&quot;Capitalize name&quot;, &quot;Capitalize name of &#39;blog&#39;&quot;, &#39;&#39;&#39;
entity Blog {
}
&#39;&#39;&#39;)
)
}
..
}}
&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&quot;new-project-wizard&quot;&gt;New Project Wizard&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The New Xtext Project wizard selects JUnit 5 as default now.&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Maven&lt;/em&gt; build support: the &lt;code&gt;maven-clean-plugin&lt;/code&gt; configuration in the parent &lt;code&gt;pom.xml&lt;/code&gt; has been fixed.&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Gradle&lt;/em&gt; build support: Upgrade to Gradle wrapper 4.10.2.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;xbase-library&quot;&gt;Xbase Library&lt;/h2&gt;
&lt;p&gt;The Xbase library supports now accessors for two-dimensional arrays.&lt;/p&gt;
&lt;h2 id=&quot;parallel-project-build-support&quot;&gt;Parallel Project Build Support&lt;/h2&gt;
&lt;p&gt;With Eclipse 4.8 (Photon) the Eclipse Platform is supporting parallel build of projects in the workspace. Enabling this feature requires that all configured builders of a project are defining a fine grained scheduling rule. For the XtextBuilder the scheduling rule is configurable by preference now.&lt;/p&gt;
&lt;p&gt;The preference is not configurable through preference pages. To enable it, set the &lt;code&gt;org.eclipse.xtext.builder/schedulingrule&lt;/code&gt; preference option programmatically or by providing a preference file. The supported values are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;WORKSPACE&lt;/code&gt;: Workspace root scheduling. This is the default value.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;ALL_XTEXT_PROJECTS&lt;/code&gt;: Lock all projects with Xtext nature configured. Allows projects of other natures to be built in parallel.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;PROJECT&lt;/code&gt;: Locks the currently built project.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;NULL&lt;/code&gt;: No locking&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This feature is &lt;em&gt;experimental&lt;/em&gt; for now.&lt;/p&gt;
&lt;h2 id=&quot;language-server-support&quot;&gt;Language Server Support&lt;/h2&gt;
&lt;h3 id=&quot;upgrade-to-eclipse-lsp4j-060&quot;&gt;Upgrade to Eclipse LSP4J 0.6.0&lt;/h3&gt;
&lt;p&gt;Xtext 2.16 integrates Eclipse LSP4J version 0.6.0.&lt;/p&gt;
&lt;h3 id=&quot;hierarchical-document-symbols&quot;&gt;Hierarchical Document Symbols&lt;/h3&gt;
&lt;p&gt;Xtext now supports the &lt;em&gt;hierarchical document symbols&lt;/em&gt; as a response to the &lt;code&gt;textDocument/documentSymbol&lt;/code&gt; request (introduced in &lt;a href=&quot;https://microsoft.github.io/language-server-protocol/specification#version_3_10_0&quot;&gt;LSP 3.10.0&lt;/a&gt;). For this support a new interface &lt;a href=&quot;https://github.com/eclipse/xtext-core/blob/9e46f302bb7bfd68b61f1a05f1c9bb5d830b7fa1/org.eclipse.xtext.ide/src/org/eclipse/xtext/ide/server/symbol/IDocumentSymbolService.xtend&quot;&gt;&lt;code&gt;IDocumentSymbolService&lt;/code&gt;&lt;/a&gt; has been added to the bundle &lt;code&gt;org.eclipse.xtext.ide&lt;/code&gt;. By default it binds to a no-op implementation. Hierarchical symbols can be activated by binding the interface to the &lt;a href=&quot;https://github.com/eclipse/xtext-core/blob/9e46f302bb7bfd68b61f1a05f1c9bb5d830b7fa1/org.eclipse.xtext.ide/src/org/eclipse/xtext/ide/server/symbol/HierarchicalDocumentSymbolService.xtend&quot;&gt;&lt;code&gt;HierarchicalDocumentSymbolService&lt;/code&gt;&lt;/a&gt; implementation.&lt;/p&gt;
&lt;h3 id=&quot;configurable-server-exit-behavior&quot;&gt;Configurable Server Exit Behavior&lt;/h3&gt;
&lt;p&gt;The default behavior on receiving the &lt;code&gt;exit&lt;/code&gt; command of Xtext language servers was to call &lt;code&gt;System.exit&lt;/code&gt; and thus terminate the JVM. While this is desirable when a host process is shut down (like termination of the editing tool), it harms &lt;a href=&quot;https://github.com/eclipse/xtext-core/issues/885&quot;&gt;scenarios&lt;/a&gt; where the language server and client run on the same JVM.&lt;/p&gt;
&lt;p&gt;To support both use cases, the &lt;code&gt;exit&lt;/code&gt; command is now delegated to the &lt;code&gt;ILanguageServerShutdownAndExitHandler&lt;/code&gt;. Its default implementation &lt;code&gt;ILanguageServerShutdownAndExitHandler.DefaultImpl&lt;/code&gt; preserves the existing behavior and invokes &lt;code&gt;System.exit()&lt;/code&gt;. For embedded scenarios, the interface can be bound to &lt;code&gt;ILanguageServerShutdownAndExitHandler.NullImpl&lt;/code&gt; instead, which ignores the exit request and keeps the JVM alive.&lt;/p&gt;
&lt;h2 id=&quot;minimal-target-platform&quot;&gt;Minimal Target Platform&lt;/h2&gt;
&lt;p&gt;The Eclipse Platform has changed the release cadence after its Photon release (4.9) to quartely major releases. This increases the speed of changes to the platform that Xtext relies on. Since Xtext integrates deeply with the platform, its becoming harder to to support a wide range of releases. Therefore we decided to cut off the supported Eclipse releases and require at least Eclipse 4.7.3a (Oxygen.3a, latest Oxygen release).&lt;/p&gt;
&lt;p&gt;This has now been enforced by constraining the lower bound of all bundles of the Eclipse Platform. As a consequence, Xtext 2.16 can no longer be installed on an older Eclipse release.&lt;/p&gt;
&lt;h2 id=&quot;deprecation-of-gwt&quot;&gt;Deprecation of GWT&lt;/h2&gt;
&lt;p&gt;We will no longer maintain the GWT versions of Xbase and Xtend Lib. The corresponding jars will be no longer published with future versions of Xtext (likely from 2.17 on).&lt;/p&gt;
&lt;h2 id=&quot;outlook-for-217&quot;&gt;Outlook for 2.17&lt;/h2&gt;
&lt;p&gt;Java 11 Support, a Maven BOM and a new MWE version are planned for 2.17&lt;/p&gt;
&lt;h2 id=&quot;fixed-issues&quot;&gt;Fixed Issues&lt;/h2&gt;
&lt;p&gt;As in every release cycle we were eagerly hunting down bugs, and reviewed and integrated plenty of contributions. Almost 100 issues and 300 pull requests have made it into this release. For further details please refer to the following lists:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Aissue+milestone%3ARelease_2.16+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Fixed GitHub issues&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Apr+milestone%3ARelease_2.16+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Closed Pull Requests&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&amp;amp;bug_status=VERIFIED&amp;amp;bug_status=CLOSED&amp;amp;classification=Modeling&amp;amp;classification=Tools&amp;amp;columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ckeywords&amp;amp;f0=OP&amp;amp;f1=OP&amp;amp;f3=CP&amp;amp;f4=CP&amp;amp;known_name=Xtext%202.16&amp;amp;list_id=16618269&amp;amp;product=TMF&amp;amp;product=Xtend&amp;amp;query_based_on=Xtext%202.16&amp;amp;query_format=advanced&amp;amp;status_whiteboard=v2.16&amp;amp;status_whiteboard_type=allwordssubstr&quot;&gt;Fixed Eclipse Bugzilla tickets&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description>
<pubDate>Tue, 04 Dec 2018 00:00:00 +0000</pubDate>
<link>http://xtext.org/Xtext/releasenotes/2018/12/04/version-2-16-0.html</link>
<guid isPermaLink="true">http://xtext.org/Xtext/releasenotes/2018/12/04/version-2-16-0.html</guid>
<category>releasenotes</category>
</item>
<item>
<title>Xtext 2.15.0 Release Notes</title>
<description>&lt;p&gt;This release focusses on stability, performance and the integration in Eclipse 2018-09.&lt;/p&gt;
&lt;h2 id=&quot;minimal-required-target-platform&quot;&gt;Minimal Required Target Platform&lt;/h2&gt;
&lt;p&gt;Xtext and Xtend 2.15 are built and tested against Eclipse Oxygen 3a and newer. Thus we recommend to use at least Eclipse Oxygen 3a or even better Eclipse 2018-09. For older versions of the Eclipse Platform we cannot guarantee backwards compatibility even though we carefully assess any changes that are made.&lt;/p&gt;
&lt;h2 id=&quot;support-for-designated-test-source-folders&quot;&gt;Support for designated test source folders&lt;/h2&gt;
&lt;p&gt;Recently Eclipse started to support Java projects with additional source folders that are specifically used for test sources. The project layout thus is more flexible and can be aligned with Maven or Gradle defaults. Test folders are highlighted in the UI and the class path for test sources and non-test sources are separated. This ensures that production code does not reference any test code. The Xtext new project wizard now ensures that new projects mark their source folders appropriately.&lt;/p&gt;
&lt;h2 id=&quot;improved-testing-support&quot;&gt;Improved Testing Support&lt;/h2&gt;
&lt;p&gt;The Xtext UI Testing infrastructure provides the &lt;code&gt;org.eclipse.xtext.ui.testing.AbstractHighlightingTest&lt;/code&gt; base class for testing the syntactical/semantical highlighting behaviour. The Homeautomation and the State-Machine examples contain corresponding highlighting test cases to demonstrate the usage of the &lt;code&gt;AbstractHighlightingTest&lt;/code&gt; class.&lt;/p&gt;
&lt;h2 id=&quot;improved-progress-reporting&quot;&gt;Improved Progress Reporting&lt;/h2&gt;
&lt;p&gt;The progress reporting for the Xtext builder was enhanced and does now provide more detailed information about the current task. Especially for full builds it is not easier to estimate the remaining time.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_15_progressmonitor.gif&quot; alt=&quot;&quot; height=&quot;50%&quot; width=&quot;50%&quot; /&gt;&lt;/p&gt;
&lt;h2 id=&quot;task-tags-and-task-tags&quot;&gt;Task tags and TASK tags&lt;/h2&gt;
&lt;p&gt;The Xtext API for ToDo task tags now supports case sensitive patterns such that a TASK can be rendered differently than a mere Task.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_15_tasktags.png&quot; alt=&quot;&quot; height=&quot;50%&quot; width=&quot;50%&quot; /&gt;&lt;/p&gt;
&lt;h2 id=&quot;navigation-in-external-files&quot;&gt;Navigation in External Files&lt;/h2&gt;
&lt;p&gt;The editing experience for files that are not contained in a workspace has been improved. Navigation and editing works more reliable now.&lt;/p&gt;
&lt;h2 id=&quot;command-line-interface-class-for-project-creation&quot;&gt;Command line interface class for project creation&lt;/h2&gt;
&lt;p&gt;Xtext projects can be created from a command line by invoking the &lt;code&gt;org.eclipse.xtext.xtext.wizard.cli.CliProjectsCreatorMain&lt;/code&gt; main class. This class exposes all options that the New Project Wizard offers as command-line options. Call the class to see all options.&lt;/p&gt;
&lt;p&gt;Example arguments for the creation of a typical DSL targetting Eclipse UI and Maven Tycho build on Java 10:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;-targetDir=./mydsl
-languageName=org.xtext.example.mydsl.MyDsl
-baseName=org.xtext.example.mydsl
-extension=mydsl
-enabledProjects=GenericIDE,RuntimeTest,UIProject,UITest,P2Project
-buildSystem=MAVEN
-sourceLayout=PLAIN
-languageServer=APP
-xtextVersion=2.15.0
-projectLayout=FLAT
-javaVersion=JAVA10
&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&quot;api-improvements&quot;&gt;API Improvements&lt;/h2&gt;
&lt;p&gt;The API when working with the Xtext documents was improved. Convenience methods have been added that are more robust against broken document content when the model is accessed from units of work. If you don’t want to see any null resource or if you want to handle exceptions specifically when accessing the model, you may want to use &lt;a href=&quot;https://github.com/eclipse/xtext-core/blob/master/org.eclipse.xtext.util/src/org/eclipse/xtext/util/concurrent/IWriteAccess.java#L53&quot;&gt;&lt;code&gt;tryModify&lt;/code&gt;&lt;/a&gt; or &lt;code&gt;tryReadOnly&lt;/code&gt; respectively.&lt;/p&gt;
&lt;h2 id=&quot;lsp4j-050&quot;&gt;LSP4J 0.5.0&lt;/h2&gt;
&lt;p&gt;We have updated to LSP4J 0.5.0 which adds support for semantic highlighting.&lt;/p&gt;
&lt;p&gt;Although the semantic highlighting &lt;a href=&quot;https://microsoft.github.io/language-server-protocol/specification&quot;&gt;Language Server Protocol&lt;/a&gt; extension is still in a &lt;a href=&quot;https://github.com/Microsoft/vscode-languageserver-node/pull/367&quot;&gt;proposal&lt;/a&gt; state, the Xtext-based language server (LS) is one of the early adopters. The semantic highlighting information is calculated on the Xtext language server and pushed to the client as a notification. This notification carries information about the ranges that have to be colored on the client-side. The desired coloring details are given as &lt;a href=&quot;https://manual.macromates.com/en/language_grammars&quot;&gt;TextMate scopes&lt;/a&gt; for each affected range. Adopters can reuse the entire highlighting logic from the &lt;a href=&quot;https://github.com/eclipse/xtext-core/blob/f7c7a604ed9d922a3ea5595a42e6922bccd123e6/org.eclipse.xtext.ide/src/org/eclipse/xtext/ide/editor/syntaxcoloring/ISemanticHighlightingCalculator.java#L23&quot;&gt;&lt;code&gt;ISemanticHighlightingCalculator&lt;/code&gt;&lt;/a&gt; implementation as is to enable the LS-based semantic highlighting. The only thing they have to provide is a mapping between the style IDs and the desired TextMate scopes via the recently introduced &lt;a href=&quot;https://github.com/eclipse/xtext-core/blob/f7c7a604ed9d922a3ea5595a42e6922bccd123e6/org.eclipse.xtext.ide/src/org/eclipse/xtext/ide/server/semanticHighlight/ISemanticHighlightingStyleToTokenMapper.xtend#L26&quot;&gt;token mapper&lt;/a&gt;. At this state, it is a must to map each style ID to the corresponding scopes manually.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_15_semantic-highlighting.gif&quot; alt=&quot;&quot; height=&quot;50%&quot; width=&quot;50%&quot; /&gt;&lt;/p&gt;
&lt;h2 id=&quot;update-gradle-to-49&quot;&gt;Update Gradle to 4.9&lt;/h2&gt;
&lt;p&gt;We have upgraded Gradle to 4.9. New projects are built against the this version.&lt;/p&gt;
&lt;h2 id=&quot;fixed-issues&quot;&gt;Fixed Issues&lt;/h2&gt;
&lt;p&gt;As in every release cycle we were eagerly hunting down bugs, and reviewed and integrated plenty of contributions. More than a 100 issues and almost 300 pull requests have made it into this release. For further details please refer to the following lists:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Aissue+milestone%3ARelease_2.15+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Fixed GitHub issues&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Apr+milestone%3ARelease_2.15+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Closed Pull Requests&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&amp;amp;bug_status=VERIFIED&amp;amp;bug_status=CLOSED&amp;amp;classification=Modeling&amp;amp;classification=Tools&amp;amp;columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ckeywords&amp;amp;f0=OP&amp;amp;f1=OP&amp;amp;f3=CP&amp;amp;f4=CP&amp;amp;known_name=Xtext%202.15&amp;amp;list_id=16618269&amp;amp;product=TMF&amp;amp;product=Xtend&amp;amp;query_based_on=Xtext%202.15&amp;amp;query_format=advanced&amp;amp;status_whiteboard=v2.15&amp;amp;status_whiteboard_type=allwordssubstr&quot;&gt;Fixed Eclipse Bugzilla tickets&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description>
<pubDate>Tue, 04 Sep 2018 00:00:00 +0000</pubDate>
<link>http://xtext.org/Xtext/releasenotes/2018/09/04/version-2-15-0.html</link>
<guid isPermaLink="true">http://xtext.org/Xtext/releasenotes/2018/09/04/version-2-15-0.html</guid>
<category>releasenotes</category>
</item>
<item>
<title>Xtext 2.14.0 Release Notes</title>
<description>&lt;p&gt;While the Xtext project has paid more attention on bug fixing for the past release, Xtext 2.14 is bringing a whole bunch of new features. This version is part of the Eclipse Photon (4.8) simultaneous release. An important focus was to keep up with the fast development pace of important technologies that Xtext is building on. Since its past release, Java 9 and 10 came out. Build technologies like Maven Tycho and Gradle were changed to support that, too. The Language Server Protocol is evolving rapidly. JUnit 5 is adopted by IDEs and build systems. And Xtext is now ready for all of them!&lt;/p&gt;
&lt;h2 id=&quot;java-9-and-10-support&quot;&gt;Java 9 and 10 Support&lt;/h2&gt;
&lt;p&gt;Xtext and Xtend 2.14 are able to compile with and against Java 9 &amp;amp; 10. Here are a few notes on the support&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;There is no native support for Java 9/10 module visibilities but we fall back to jdt/javac on that topic.&lt;/li&gt;
&lt;li&gt;A current Maven version is required (tested with 3.5)&lt;/li&gt;
&lt;li&gt;When using Gradle, version 4.7 is required at least. The wizard will create projects accordingly.&lt;/li&gt;
&lt;li&gt;Java 9 requires Tycho 1.1 or newer, Java 10 requires Tycho 1.2&lt;/li&gt;
&lt;li&gt;Java 9 requires Oxygen.1a at least, Java 10 requires Oxygen.3a. Eclipse Photon works fine for both.&lt;/li&gt;
&lt;li&gt;Java 10 requires the org.objectweb.asm library in version 6.1.1&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For upgrading existing project use the New Project Wizard to create a project with the desired settings and compare build relevant files (MANIFEST.MF, build.gradle, pom.xml, *.target) with the existing projects.&lt;/p&gt;
&lt;h2 id=&quot;junit-5-support&quot;&gt;JUnit 5 Support&lt;/h2&gt;
&lt;p&gt;Xtext now supports the JUnit 5 framework for writing tests. JUnit 5.1 or newer is required.&lt;/p&gt;
&lt;p&gt;For new projects the project wizard’s advanced page allows to select the desired JUnit version.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_14_wizard_junit5.gif&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;
&lt;p&gt;Created test projects directly only depend on the JUnit 5 API artifact&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;org.junit.jupiter:junit-jupiter-api:5.0.0
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Additional dependencies are configured by the JUnit Library container. This lowers the coupling to concrete JUnit versions and the test engine used. For example, Eclipse Photon is using JUnit 5.1, while Eclipse Oxygen is using JUnit 5.0. Furthermore, the execution of tests in build systems is using the test engines provided by the build system’s test plugins.&lt;/p&gt;
&lt;h2 id=&quot;new-grammar-annotations&quot;&gt;New Grammar Annotations&lt;/h2&gt;
&lt;p&gt;The Xtext Grammar language supports the following additional annotations for parser rules:&lt;/p&gt;
&lt;h3 id=&quot;deprecated&quot;&gt;@Deprecated&lt;/h3&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_14_annotation_deprecated.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;
&lt;p&gt;This annotation marks a rule to be deprecated. Issue markers with are produced where a deprecated rule is used. By default the severity of issue is &lt;em&gt;Warning&lt;/em&gt;. The severity level can be configured in the preferences. This feature will help you to do smooth langauage evolution of the time by informing your users about deprecated parts.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_14_annotation_preference.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;
&lt;h3 id=&quot;final&quot;&gt;@Final&lt;/h3&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_14_annotation_final.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;
&lt;p&gt;A rule marked with &lt;code&gt;@Final&lt;/code&gt; cannot be overridden.&lt;/p&gt;
&lt;h3 id=&quot;exported&quot;&gt;@Exported&lt;/h3&gt;
&lt;p&gt;As a default Xtext exports all elements to the index that have a name. For customizing this behaviour you need to create a custom IDefaultResourceDescriptionStrategy manually.&lt;br /&gt;
With &lt;code&gt;@Exported&lt;/code&gt; it can be customized on grammar level, which element types are exported to the index. The customization takes effect when at least one rule in a grammar is annotated with &lt;code&gt;@Exported&lt;/code&gt;. By doing that you can easily manage visibility of elements and safe memory.&lt;/p&gt;
&lt;h2 id=&quot;eclipse-integration&quot;&gt;Eclipse Integration&lt;/h2&gt;
&lt;h3 id=&quot;create-action-quickfix&quot;&gt;Create Action Quickfix&lt;/h3&gt;
&lt;p&gt;Rules that can be consumed without object instantiation usually require a &lt;em&gt;Create Action&lt;/em&gt;. A typical example is when a rule defines an optional assignment. Xtext reports this as a warning in the grammar file.&lt;/p&gt;
&lt;p&gt;For problems of this kind a new &lt;em&gt;quickfix&lt;/em&gt; has been added that inserts the &lt;em&gt;Create Action&lt;/em&gt; at the proper place of the parser rule.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_14_create-action.gif&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;
&lt;h3 id=&quot;code-mining-support&quot;&gt;Code Mining Support&lt;/h3&gt;
&lt;p&gt;Eclipse Photon (4.8) adds a new API called &lt;em&gt;Code Mining&lt;/em&gt;. With it text editors can inline additional semantic information into the text, which is not part of the text itself. A useful example to leverage this is to display names of inferred types, parameter names of a called function etc.&lt;/p&gt;
&lt;p&gt;Xtext adds a new bundle &lt;code&gt;org.eclipse.xtext.ui.codemining&lt;/code&gt; which is offering an API for usage of Code Mining with Xtext. The code generator fragment &lt;code&gt;org.eclipse.xtext.xtext.generator.ui.codemining.CodeMiningFragment&lt;/code&gt; can be added to the generator workflow to create a stub implementation and provide all dependencies and bindings for the use of this API.&lt;/p&gt;
&lt;p&gt;An example implementation has been added to the Domainmodel Example DSL. To learn more about the usage of this API install the example from the File menu and look up the &lt;code&gt;DomainmodelCodeMiningProvider&lt;/code&gt; class.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_14_domainmodel-codemining.gif&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;
&lt;h3 id=&quot;new-project-and-file-wizard&quot;&gt;New Project and File Wizard&lt;/h3&gt;
&lt;p&gt;With two simple switches you can turn on the generation of a New Project Wizard and a New File Wizard for your language.&lt;/p&gt;
&lt;p&gt;These wizards are based on flexible templates to generate one or many projects with any number of files. You can enable the generation from your .mwe2 file with two simple switches:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;language = StandardLanguage {
name = &quot;org.xtext.example.mydsl.MyDsl&quot;
fileExtensions = &quot;mydsl&quot;
fileWizard = {
generate = true
}
projectWizard = {
generate = true
}
}
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The wizard to create projects allows to select from a number of templates and creates one or, in certain situations helpful, even many projects.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_14_new-file-wizard.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;
&lt;p&gt;The wizard to create files is more simple in its basic form and skips the template selection if there is only one file template.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_14_new-project-wizard-template-selection.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;
&lt;p&gt;In case there are many templates the wizard gets a second page to configure the parameter whereas on the first page a combo box to select the template appears.&lt;/p&gt;
&lt;p&gt;The UI for the parameters of the templates as well as the templates them self are defined in code with a concise API. You do not need to fiddle around with SWT widgets and get most UI stuff for free. The templates are generated in the UI project of your language. You can adapt the generated templates, add new ones or contribute new template providers through extension points.&lt;/p&gt;
&lt;p&gt;If you generate the wizards for an existing project the &lt;code&gt;plugin.xml&lt;/code&gt; is not regenerated to not risk loosing manual changes you might have applied. Instead a &lt;code&gt;plugin.xml_gen&lt;/code&gt; is created. You have to merge the generated extensions to your &lt;code&gt;plugin.xml&lt;/code&gt; manually.&lt;/p&gt;
&lt;h3 id=&quot;console-icon&quot;&gt;Console Icon&lt;/h3&gt;
&lt;p&gt;The Xtext icon has been added for the Xtext console:&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_14_console-icon.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;
&lt;h2 id=&quot;language-server-support&quot;&gt;Language Server Support&lt;/h2&gt;
&lt;p&gt;Xtext has been upgraded to LSP4J version 0.4.0. This includes the following features:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Implementation of the Language Server Protocol 3.7.0&lt;/li&gt;
&lt;li&gt;Implementation of the VS Code Debug Protocol 1.25.0&lt;/li&gt;
&lt;li&gt;Support multiple local and remote services&lt;/li&gt;
&lt;li&gt;Improved error handling&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;emf-support&quot;&gt;EMF Support&lt;/h2&gt;
&lt;p&gt;With EMF 2.14 a new registry &lt;code&gt;EAnnotationValidator.Registry.INSTANCE&lt;/code&gt;, which had to be considered in Xtext’s testing support for resetting.&lt;/p&gt;
&lt;p&gt;EMF 2.8 &lt;a href=&quot;https://bugs.eclipse.org/bugs/show_bug.cgi?id=367569#c7&quot;&gt;introduced&lt;/a&gt; the concept &lt;code&gt;ResourceLocator&lt;/code&gt; in &lt;code&gt;ResourceSet&lt;/code&gt;s. Xtext’s specialized implementation &lt;code&gt;XtextResourceSet&lt;/code&gt; did not support that so far and has been extended now.&lt;/p&gt;
&lt;h2 id=&quot;change-serializer--rename-refactoring&quot;&gt;Change Serializer &amp;amp; Rename Refactoring&lt;/h2&gt;
&lt;p&gt;The past &lt;a href=&quot;/Xtext/releasenotes.html#/releasenotes/2017/10/20/version-2-13-0&quot;&gt;release 2.13&lt;/a&gt; introduced a new API for EMF Model Manipulation and an improved rename refactoring based on the new &lt;code&gt;IChangeSerializer&lt;/code&gt; API.&lt;/p&gt;
&lt;p&gt;These new features are still incubating. Several issues that were identified by the adoption of the features have been solved.&lt;/p&gt;
&lt;h2 id=&quot;performance&quot;&gt;Performance&lt;/h2&gt;
&lt;h3 id=&quot;output-configurations-cache&quot;&gt;Output Configurations Cache&lt;/h3&gt;
&lt;p&gt;A performance bottleneck was &lt;a href=&quot;https://github.com/eclipse/xtext-eclipse/issues/535&quot;&gt;discovered&lt;/a&gt; in the access to &lt;code&gt;IOutputConfiguration&lt;/code&gt;s in builder participants. The problem depends on the amount of files produced by code generators.&lt;/p&gt;
&lt;p&gt;A cache was introduced in class &lt;code&gt;BuilderParticipant&lt;/code&gt; to solve the issue.&lt;/p&gt;
&lt;h3 id=&quot;semantic-highlighting&quot;&gt;Semantic Highlighting&lt;/h3&gt;
&lt;p&gt;Computation of semantic highlighting &lt;a href=&quot;https://github.com/eclipse/xtext-eclipse/issues/347&quot;&gt;was performed twice&lt;/a&gt;. This was fixed and should improve editing experience especially for larger files with intensive use of semantic highlighting, for example like the Xtend language.&lt;/p&gt;
&lt;h3 id=&quot;queuedbuilddata&quot;&gt;QueuedBuildData&lt;/h3&gt;
&lt;p&gt;A bottleneck in class &lt;code&gt;QueuedBuildData&lt;/code&gt; has been &lt;a href=&quot;https://github.com/eclipse/xtext-eclipse/issues/40&quot;&gt;found&lt;/a&gt; that affects the build time for a large number of resources. The build time has been improved for this scenario.&lt;/p&gt;
&lt;h2 id=&quot;execution-environment&quot;&gt;Execution Environment&lt;/h2&gt;
&lt;p&gt;Xtext 2.14 comes with the following requirements for the execution environment:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Java: 1.8, 9 or 10&lt;/li&gt;
&lt;li&gt;Eclipse Luna (4.4) or newer&lt;/li&gt;
&lt;li&gt;EMF 2.10 or newer&lt;/li&gt;
&lt;li&gt;Guice 3.0&lt;/li&gt;
&lt;li&gt;Tycho 1.1, 1.2 (Java 10 or JUnit 5)&lt;/li&gt;
&lt;li&gt;JUnit 4.12 or 5.1&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Note that bundle &lt;code&gt;org.eclipse.xtext.xbase.lib&lt;/code&gt; was compiled with Java 1.8 now, while being compatible to 1.6 in earlier versions.&lt;/p&gt;
&lt;h2 id=&quot;links&quot;&gt;Links&lt;/h2&gt;
&lt;p&gt;More detailed information on some topics have been written in blog posts:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://blogs.itemis.com/en/xtext-2.14-adds-support-for-junit-5&quot;&gt;“Xtext 2.14 adds support for JUnit 5”&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://blogs.itemis.com/en/code-mining-support-in-xtext&quot;&gt;“Code Mining Support in Xtext”&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://blogs.itemis.com/en/generating-a-new-project-wizard-with-xtext-2.14&quot;&gt;“Generating a new project wizard with Xtext 2.14”&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://blogs.itemis.com/en/new-file-wizard-easy-to-generate-with-xtext-2.14&quot;&gt;“New File Wizard – easy to generate with Xtext 2.14”&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://blogs.itemis.com/de/new-project-wizard-einfach-mit-xtext-2-14-generieren&quot;&gt;“New Project Wizard: einfach mit Xtext 2.14 generieren”&lt;/a&gt; (German)&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://blogs.itemis.com/de/new-file-wizard-einfach-mit-xtext-2.14-generieren&quot;&gt;“Erzeugen des New File Wizards”&lt;/a&gt; (German)&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/eclipse/lsp4j/blob/master/CHANGELOG.md&quot;&gt;LSP4J Changelog&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;fixed-issues&quot;&gt;Fixed Issues&lt;/h2&gt;
&lt;p&gt;As in every release we are eagerly hunting down the bugs, review and integrate lots of contributions. 88 issues, 62 Pull Requests and 60 Bugzilla tickets have made it into this release. For further details please refer to the following lists:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Aissue+milestone%3ARelease_2.14+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Fixed GitHub issues&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Apr+milestone%3ARelease_2.14+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Closed Pull Requests&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&amp;amp;bug_status=VERIFIED&amp;amp;bug_status=CLOSED&amp;amp;classification=Modeling&amp;amp;classification=Tools&amp;amp;columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ckeywords&amp;amp;f0=OP&amp;amp;f1=OP&amp;amp;f3=CP&amp;amp;f4=CP&amp;amp;known_name=Xtext%202.14&amp;amp;list_id=16618269&amp;amp;product=TMF&amp;amp;product=Xtend&amp;amp;query_based_on=Xtext%202.14&amp;amp;query_format=advanced&amp;amp;status_whiteboard=v2.14&amp;amp;status_whiteboard_type=allwordssubstr&quot;&gt;Fixed Eclipse Bugzilla tickets&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description>
<pubDate>Wed, 23 May 2018 00:00:00 +0000</pubDate>
<link>http://xtext.org/Xtext/releasenotes/2018/05/23/version-2-14-0.html</link>
<guid isPermaLink="true">http://xtext.org/Xtext/releasenotes/2018/05/23/version-2-14-0.html</guid>
<category>releasenotes</category>
</item>
<item>
<title>Xtext 2.13.0 Release Notes</title>
<description>&lt;h2 id=&quot;language-server-support&quot;&gt;Language Server Support&lt;/h2&gt;
&lt;h3 id=&quot;eclipse-new-project-wizard-language-server-build&quot;&gt;Eclipse New Project Wizard: Language Server Build&lt;/h3&gt;
&lt;p&gt;The New Project Wizard allows now to build an executable distribution of language server. On the advanced page a new option was added which is enabled when a Build System was selected. The option allows the selection of a distribution type:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Regular&lt;/strong&gt;: A batch script is created that is used to start the server. The DSL jars and all of its runtime dependencies are copied to the output folder.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fat Jar&lt;/strong&gt;: The language server is packaged in a single executable jar.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Both Gradle and Maven are supported. When activated, the build script of the language’s Generic IDE project is extended and the language server is packaged to the project’s build&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_13_project-wizard-ls.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;
&lt;h2 id=&quot;eclipse-integration&quot;&gt;Eclipse Integration&lt;/h2&gt;
&lt;h3 id=&quot;configuration-error-detection&quot;&gt;Configuration Error Detection&lt;/h3&gt;
&lt;p&gt;Invalid combinations of bundles are a frequent source of errors. This can be caused by an invalid mixture of Xtext’s UI and runtime plugins, or by DSL plugins developed with a different version of Xtext than used in the environment where it fails.&lt;/p&gt;
&lt;p&gt;Although there can’t be done anything to get the plugins working on an invalid environment, the resulting failure messages were not good for the user, leaving an impression of an unstable framework.&lt;/p&gt;
&lt;p&gt;When running in an error during the initial creation of Guice injectors in the DSL’s UI or Xtext’s Shared UI bundle, the error is catched and an analysis of the runtime environment is included in the failure message. This allows better analysis of the root cause.&lt;/p&gt;
&lt;h3 id=&quot;multi-quickfixes&quot;&gt;Multi-Quickfixes&lt;/h3&gt;
&lt;p&gt;These are quickfixes that allow to be applied to multiple markers at once.&lt;/p&gt;
&lt;p&gt;TBD&lt;/p&gt;
&lt;h3 id=&quot;better-cancellation-in-refactorings&quot;&gt;Better Cancellation in Refactorings&lt;/h3&gt;
&lt;p&gt;You can how hit the cancel dialog in refactorings and it will actually cancel at the next opportunity and not at the end only.&lt;/p&gt;
&lt;h3 id=&quot;content-type-descriptor&quot;&gt;Content Type Descriptor&lt;/h3&gt;
&lt;p&gt;Xtext UI projects provide a Content Type Descriptor by contributing to the &lt;a href=&quot;https://help.eclipse.org/oxygen/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fruntime_content_contributing.htm&quot;&gt;&lt;code&gt;org.eclipse.core.contenttype.contentTypes&lt;/code&gt; extension point&lt;/a&gt; to the &lt;code&gt;plugin.xml&lt;/code&gt; file. This is affecting performance on text searches in Eclipse, since Eclipse can decide that a DSL file has no binary content based on the content type’s base type. (&lt;a href=&quot;https://github.com/eclipse/xtext-eclipse/issues/379&quot;&gt;xtext-eclipse/issues/379&lt;/a&gt;)&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;&amp;lt;extension point=&quot;org.eclipse.core.contenttype.contentTypes&quot;&amp;gt;
&amp;lt;content-type
base-type=&quot;org.eclipse.core.runtime.text&quot;
file-extensions=&quot;mydsl&quot;
id=&quot;org.eclipse.xtext.mydsl.MyDSL.contenttype&quot;
name=&quot;MyDSL File&quot;
priority=&quot;normal&quot;&amp;gt;
&amp;lt;/content-type&amp;gt;
&amp;lt;/extension&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&quot;new-api&quot;&gt;New API&lt;/h2&gt;
&lt;h3 id=&quot;emf-model-manipulation-api-incubating&quot;&gt;EMF Model Manipulation API (incubating)&lt;/h3&gt;
&lt;p&gt;The &lt;code&gt;IChangeSerializer&lt;/code&gt; is a new API to listen to changes that are made to the EMF model of an XtextResource and serialize them back to the document’s text. It has a number of benefits to the old &lt;code&gt;XtextDocument.modify()&lt;/code&gt; approach:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Direct integration with the formatter, such that changes are automatically nicely formatted.&lt;/li&gt;
&lt;li&gt;Minimum text region changes resulting in less noise.&lt;/li&gt;
&lt;li&gt;Many points to hook into, e.g. for automatic update of an import section.&lt;/li&gt;
&lt;li&gt;More ways to optimize for a specific language and to tune performance.&lt;/li&gt;
&lt;li&gt;Independence from Eclipse-UI concepts like the &lt;code&gt;Document&lt;/code&gt;. This makes it reusable in languages server implementations.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can use the &lt;code&gt;IChangeSerializer&lt;/code&gt; for refactorings, semantic quickfixes, code lens etc. It still has a few limitations, e.g. it does not work with derived state models, that’s why we keep it provisional for now.&lt;/p&gt;
&lt;p&gt;Nevertheless, we have added the following new features based on it:&lt;/p&gt;
&lt;h3 id=&quot;rename-participants-for-eclipse-file-operations&quot;&gt;Rename Participants for Eclipse File Operations&lt;/h3&gt;
&lt;p&gt;Some languages tie the model file name to the content, like the package declaration in Java. For such cases you might want to participate in operations on files or directories, like move, rename or paste, to adapt your models automatically. Based on the new &lt;code&gt;IChangeSerializer&lt;/code&gt; we have implemented some generic file refactoring participants. You will get notified of such changes to react appropriately by registering your own &lt;code&gt;IResourceRelocationStrategy&lt;/code&gt;.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;&amp;lt;extension point=&quot;org.eclipse.xtext.ui.resourceRelocationStrategy&quot;&amp;gt;
&amp;lt;strategy class=&quot;mydsl.MydslExecutableExtensionFactory:mydsl.MydslResourceRelocationStrategy&quot;&amp;gt;
&amp;lt;/strategy&amp;gt;
&amp;lt;/extension&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&quot;alternative-rename-refactoring-for-xtext&quot;&gt;Alternative Rename Refactoring for Xtext&lt;/h3&gt;
&lt;p&gt;By enabling &lt;code&gt;useChangeSerializer&lt;/code&gt; flag in the workflow of your language&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Workflow {
component = XtextGenerator {
...
language = StandardLanguage {
...
renameRefactoring = {
useChangeSerializer = true
...
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;you will use an new, alternative rename refactoring for Eclipse based on the &lt;code&gt;IChangeSerializer&lt;/code&gt;. This flag will also generate the binding for the &lt;code&gt;IRenameService&lt;/code&gt; and thereby enable rename refactoring on your language server.&lt;/p&gt;
&lt;h3 id=&quot;xbase-library-orgeclipsextextxbaselib&quot;&gt;Xbase Library (&lt;code&gt;org.eclipse.xtext.xbase.lib&lt;/code&gt;)&lt;/h3&gt;
&lt;h4 id=&quot;no-arg-overloads-to-all-mutable-collection-literals&quot;&gt;No-arg overloads to all mutable collection literals&lt;/h4&gt;
&lt;p&gt;Class &lt;code&gt;CollectionLiterals&lt;/code&gt; was extended by no-arg methods for all mutable collection literals:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;newArrayList()&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;newHashMap()&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;newHashSet()&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;newLinkedHashMap()&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;newLinkedHashSet()&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;newLinkedList()&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Xtext’s code base was refactored to use these methods where appropriate. As a consequence Xtext requires at least version 2.13 of &lt;code&gt;org.eclipse.xtext.xbase.lib&lt;/code&gt;. Therefore bundle manifests were refactored to constraint the library bundle’s lower version. New projects will automatically add the version constraint to manifests.&lt;/p&gt;
&lt;h4 id=&quot;flatmap-extension-method&quot;&gt;flatMap extension method&lt;/h4&gt;
&lt;p&gt;A new convenience method &lt;code&gt;flatMap&lt;/code&gt; has been added to &lt;code&gt;IterableExtensions&lt;/code&gt; and &lt;code&gt;IteratorExtensions&lt;/code&gt;, which combines &lt;code&gt;map&lt;/code&gt; and &lt;code&gt;flatten&lt;/code&gt;.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;@FinalFieldsConstructor
@Accessors
class Planet {
final String name
final List&amp;lt;Moon&amp;gt; moons
}
@FinalFieldsConstructor
@Accessors
class Moon {
final String name
}
class Planets {
def static void main (String[] args) {
val Iterable&amp;lt;Planet&amp;gt; planets = #[
new Planet(&quot;Earth&quot;, #[new Moon (&quot;Moon&quot;)]),
new Planet(&quot;Mars&quot;, #[new Moon (&quot;Phobos&quot;), new Moon(&quot;Deimos&quot;)])
]
val moonNames_old = planets.map[moons].flatten.map[name]
val moonNames_new = planets.flatMap[moons].map[name]
}
}
&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&quot;tracing&quot;&gt;Tracing&lt;/h2&gt;
&lt;p&gt;Tracing can now be used for debugging in generated Java code as well. The &lt;code&gt;@Traced&lt;/code&gt; annotation now takes optionally a &lt;code&gt;useForDebugging=true&lt;/code&gt;. The &lt;code&gt;@TracedAccessors&lt;/code&gt; are now adds to the &lt;code&gt;._&amp;lt;feature&amp;gt;()&lt;/code&gt; extension method a &lt;code&gt;._&amp;lt;feature&amp;gt;(useForDebugging)&lt;/code&gt; extension method.&lt;/p&gt;
&lt;h2 id=&quot;refactoring&quot;&gt;Refactoring&lt;/h2&gt;
&lt;h3 id=&quot;jdt-dependency-reduction&quot;&gt;JDT Dependency Reduction&lt;/h3&gt;
&lt;p&gt;Xtext languages can be deployed in environments without JDT UI. In some use cases it was detected that this can still lead to runtime errors due to (&lt;code&gt;NoClassDefFoundError&lt;/code&gt;). Dependencies in the following bundles have been resolved:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;org.eclipse.xtext.builder&lt;/code&gt; (&lt;a href=&quot;https://github.com/eclipse/xtext-eclipse/issues/386&quot;&gt;issue#386&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;&lt;code&gt;org.eclipse.xtext.xbase.ui&lt;/code&gt; (&lt;a href=&quot;https://bugs.eclipse.org/bugs/show_bug.cgi?id=509630&quot;&gt;bug#509630&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We reduced usage of internal API which is subject for removal in JDT. Since older Xtext versions rely on this API, the API is kept by the JDT team for backwards compatibility of Xtext. (&lt;a href=&quot;https://bugs.eclipse.org/bugs/show_bug.cgi?id=525462&quot;&gt;bug#525462&lt;/a&gt;)&lt;/p&gt;
&lt;h3 id=&quot;improved-support-for-indentation-based-languages&quot;&gt;Improved Support for Indentation Based Languages&lt;/h3&gt;
&lt;p&gt;Token placement for INDENT / DEDENT tokens have been improved. This improves content assist for indentation based languages. (&lt;a href=&quot;https://github.com/eclipse/xtext-core/pull/366&quot;&gt;issue#366&lt;/a&gt;)&lt;/p&gt;
&lt;h3 id=&quot;new-generator-infrastructure&quot;&gt;New Generator Infrastructure&lt;/h3&gt;
&lt;p&gt;Xtext 2.9 introduced a new generator infrastructure. While new projects created with Xtext and the main languages in Xtext already used this generator, there were still some languages, especially test languages, that still used the deprecated old infrastructure. All languages are now migrated to the new generator.&lt;/p&gt;
&lt;h2 id=&quot;an-eye-on-quality&quot;&gt;An Eye on Quality&lt;/h2&gt;
&lt;p&gt;With every release we are working hard on fixing as many bugs as possible. Besides our Bugtrackers Eclipse Bugzilla and GitHub Issues the &lt;a href=&quot;https://www.codetrails.com/error-analytics/&quot;&gt;Automatic Error Reporting System&lt;/a&gt; at Eclipse (AERI) is an incredible valuable source of information for us. It uncovers real problems by real users, and has made error reporting to Eclipse a no-brainer.&lt;/p&gt;
&lt;p&gt;As Xtext is a complex framework with an incredible flexibility, much can go wrong. Often these errors indicate ways of usage which we could not predict, or they show problems in custom DSLs. Sometimes they uncover also errors in code that we use. We are actively visiting the reports we get into EARI, with a focus on frequently occuring events and new ones.&lt;/p&gt;
&lt;p&gt;The Xtext team is proud that this continuous effort finally pays off. For the first time ever, we had several weeks with no new problem report. And fighting against the existing issues no a clear burn-down curve (see the Incidents Timeline). From all problems reported to AERI, we have just ~12% open, and the most frequent and urgent ones are solved.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/Xtext/images/releasenotes/2_13_aeri_problem_status.png&quot; alt=&quot;&quot; /&gt;&lt;br /&gt;
&lt;img src=&quot;/Xtext/images/releasenotes/2_13_aeri_problem_resolution.png&quot; alt=&quot;&quot; /&gt;&lt;br /&gt;
&lt;img src=&quot;/Xtext/images/releasenotes/2_13_aeri_incidents_timeline.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;
&lt;h2 id=&quot;improved-developer-contribution-support&quot;&gt;Improved Developer Contribution Support&lt;/h2&gt;
&lt;p&gt;Setting up a developer workspace has never been so easy! We have reviewed and updated our Oomph Setup which allows you to create an Eclipse development environment for Xtext with a few clicks. Just get the &lt;a href=&quot;https://www.eclipse.org/downloads/&quot;&gt;Eclipse Installer&lt;/a&gt;, go to Advanced Mode and select the Xtext subprojects you are working with. Let the Installer do the rest of the work while getting a fresh coffee.&lt;/p&gt;
&lt;h3 id=&quot;execution-environment&quot;&gt;Execution Environment&lt;/h3&gt;
&lt;p&gt;Minimal requirements are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Java 8&lt;/li&gt;
&lt;li&gt;Eclipse Luna&lt;/li&gt;
&lt;li&gt;EMF 2.10&lt;/li&gt;
&lt;li&gt;Guice 3.0&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Xtext has been tested also on Eclipse Oxygen.1a and Eclipse Photon M2.&lt;/p&gt;
&lt;h2 id=&quot;some-words-on-java-9&quot;&gt;Some words on Java 9&lt;/h2&gt;
&lt;p&gt;Java 9 Support in Eclipse Oxygen 1a and Xtext 2.13 is not yet in a perfect state. To be able to run mwe workflows you need either to remove &lt;code&gt;org.objectweb.asm&lt;/code&gt; from the mwe classpath (adapting manifest or build.properties) or install ASM 6.0 from the latest Eclipse Orbit repositories. The Compilation of Xtext projects with Java 9 is terrible slow due to a know &lt;a href=&quot;https://bugs.eclipse.org/bugs/show_bug.cgi?id=526209&quot;&gt;bug&lt;/a&gt; in JDT. So using Xtext 2.13 and Java 9 in production should be considered thrice and is not recommended. Setting the compiler level to 1.8 mitigates the performance issue slightly.&lt;/p&gt;
&lt;h2 id=&quot;fixed-issues&quot;&gt;Fixed Issues&lt;/h2&gt;
&lt;p&gt;As in every release we are eagerly hunting down the bugs, review and integrate lots of contributions. 88 issues, 62 Pull Requests and 60 Bugzilla tickets have made it into this release. For further details please refer to the following lists:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Aissue+milestone%3ARelease_2.13+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Fixed GitHub issues&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/search?utf8=%E2%9C%93&amp;amp;q=is%3Apr+milestone%3ARelease_2.13+is%3Aclosed+repo%3Aeclipse%2Fxtext+repo%3Aeclipse%2Fxtext-core+repo%3Aeclipse%2Fxtext-lib+repo%3Aeclipse%2Fxtext-extras+repo%3Aeclipse%2Fxtext-eclipse+repo%3Aeclipse%2Fxtext-idea+repo%3Aeclipse%2Fxtext-web+repo%3Aeclipse%2Fxtext-maven+repo%3Aeclipse%2Fxtext-xtend&amp;amp;type=Issues&amp;amp;ref=searchresults&quot;&gt;Closed Pull Requests&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&amp;amp;bug_status=VERIFIED&amp;amp;bug_status=CLOSED&amp;amp;classification=Modeling&amp;amp;classification=Tools&amp;amp;columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ckeywords&amp;amp;f0=OP&amp;amp;f1=OP&amp;amp;f3=CP&amp;amp;f4=CP&amp;amp;known_name=Xtext%202.13&amp;amp;list_id=16618269&amp;amp;product=TMF&amp;amp;product=Xtend&amp;amp;query_based_on=Xtext%202.13&amp;amp;query_format=advanced&amp;amp;status_whiteboard=v2.13&amp;amp;status_whiteboard_type=allwordssubstr&quot;&gt;Fixed Eclipse Bugzilla tickets&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description>
<pubDate>Fri, 20 Oct 2017 00:00:00 +0000</pubDate>
<link>http://xtext.org/Xtext/releasenotes/2017/10/20/version-2-13-0.html</link>
<guid isPermaLink="true">http://xtext.org/Xtext/releasenotes/2017/10/20/version-2-13-0.html</guid>
<category>releasenotes</category>
</item>
</channel>
</rss>