Generated from commit: https://github.com/eclipse/xtext/commit/874cbab0f6299d9828c7f9f924eceef73d88ed94
diff --git a/documentation/350_continuous_integration.html b/documentation/350_continuous_integration.html
index e999af9..521ab2e 100644
--- a/documentation/350_continuous_integration.html
+++ b/documentation/350_continuous_integration.html
@@ -274,7 +274,7 @@
<dependency>
<groupId>org.eclipse.emf</groupId>
<artifactId>org.eclipse.emf.mwe2.launch</artifactId>
- <version>2.11.2</version>
+ <version>2.11.3</version>
</dependency>
<dependency>
<groupId>org.eclipse.xtext</groupId>
@@ -413,6 +413,14 @@
</thead>
<tbody>
<tr>
+ <td><a href="http://download.eclipse.org/modeling/tmf/xtext/updates/releases/2.22.0/">2.22.0</a></td>
+ <td><a href="http://download.eclipse.org/modeling/emf/emf/builds/release/2.22">2.22.0</a> (2.20.0)</td>
+ <td><a href="http://download.eclipse.org/modeling/emft/mwe/updates/releases/2.11.3/">2.11.3</a> (2.9.1)</td>
+ <td><a href="http://download.eclipse.org/modeling/m2t/xpand/updates/releases/R201605260315">2.2.0</a> (1.4)</td>
+ <td><a href="http://download.eclipse.org/releases/2020-06">4.16.0</a> (4.7.3)</td>
+ <td><a href="http://download.eclipse.org/releases/2020-06">2020-06</a></td>
+ </tr>
+ <tr>
<td><a href="http://download.eclipse.org/modeling/tmf/xtext/updates/releases/2.21.0/">2.21.0</a></td>
<td><a href="http://download.eclipse.org/modeling/emf/emf/builds/release/2.21">2.21.0</a> (2.20.0)</td>
<td><a href="http://download.eclipse.org/modeling/emft/mwe/updates/releases/2.11.2/">2.11.2</a> (2.9.1)</td>
@@ -543,7 +551,7 @@
</tbody>
</table>
-<p>The following is an example target platform definition for Xtext 2.21.0 and Eclipse 4.15 alias 2020-03.</p>
+<p>The following is an example target platform definition for Xtext 2.22.0 and Eclipse 4.16 alias 2020-06.</p>
<pre><code class="language-xml"><?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?pde version="3.8"?>
@@ -551,7 +559,7 @@
<locations>
<location includeAllPlatforms="false" includeConfigurePhase="false" includeMode="planner" includeSource="false" type="InstallableUnit">
<unit id="org.eclipse.xtext.sdk.feature.group" version="0.0.0"/>
- <repository location="http://download.eclipse.org/modeling/tmf/xtext/updates/releases/2.21.0/"/>
+ <repository location="http://download.eclipse.org/modeling/tmf/xtext/updates/releases/2.22.0/"/>
</location>
<location includeAllPlatforms="false" includeConfigurePhase="false" includeMode="planner" includeSource="false" type="InstallableUnit">
<unit id="org.eclipse.jdt.feature.group" version="0.0.0"/>
@@ -563,7 +571,7 @@
<unit id="org.eclipse.xtend" version="0.0.0"/>
<unit id="org.eclipse.xtend.typesystem.emf" version="0.0.0"/>
<unit id="org.eclipse.emf.mwe2.launcher.feature.group" version="0.0.0"/>
- <repository location="http://download.eclipse.org/releases/2020-03/"/>
+ <repository location="http://download.eclipse.org/releases/2020-06/"/>
</location>
</locations>
</target>
diff --git a/download.html b/download.html
index 2d9d1b1..970ee42 100644
--- a/download.html
+++ b/download.html
@@ -136,7 +136,7 @@
</p>
<p>
- <strong><a href="releasenotes.html">Xtext 2.21.0 Release Notes</a></strong>
+ <strong><a href="releasenotes.html">Xtext 2.22.0 Release Notes</a></strong>
</p>
</div>
diff --git a/feed.xml b/feed.xml
index 101536f..918898e 100644
--- a/feed.xml
+++ b/feed.xml
@@ -6,11 +6,105 @@
</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 14:39:30 +0000</pubDate>
- <lastBuildDate>Tue, 02 Jun 2020 14:39:30 +0000</lastBuildDate>
+ <pubDate>Tue, 02 Jun 2020 16:56:47 +0000</pubDate>
+ <lastBuildDate>Tue, 02 Jun 2020 16:56:47 +0000</lastBuildDate>
<generator>Jekyll v2.5.3</generator>
<item>
+ <title>Xtext 2.22.0 Release Notes</title>
+ <description><p>Xtext 2.22.0 is mainly a maintenance release.</p>
+
+<h2 id="call-to-action-secure-the-future-maintenance-of-xtext">Call to Action: Secure the future maintenance of Xtext</h2>
+
+<p>As you might have recognized, the number of people contributing to Xtext on a regular basis has declined over the past years and so has the number of contributions. At the same time the amount of work for basic maintenance has stayed the same or even increased with the new release cadence of Java and the Eclipse simultaneous release. Briefly: The future maintenance of Xtext is at risk. If you care, please join the discussion in <a href="https://github.com/eclipse/xtext/issues/1721">https://github.com/eclipse/xtext/issues/1721</a>.</p>
+
+<h2 id="documentation">Documentation</h2>
+
+<p>The <a href="https://www.eclipse.org/Xtext/community.html">Xtext community website</a> and the <a href="https://www.eclipse.org/Xtext/documentation/index.html">Xtext documentation website</a> have been updated. New Xtext-based projects have been added, some editor features and the Unit testing / UI testing capabilities have been documented and the embedded code snippets have been updated as well.</p>
+
+<p>We further enhanced the <a href="https://github.com/eclipse/xtext/tree/master/dev-doc">Xtext Developer Documentation</a> to enable the community to easily contribute to Xtext.</p>
+
+<h2 id="code-generation-improvements">Code Generation improvements</h2>
+<p>This release contains some fixes to improve the generated code in the <code>src-gen</code> folders. The following files are affected:</p>
+
+<ul>
+ <li><code>Internal&lt;dslName&gt;.g</code> file in the <strong>runtime</strong> module - <a href="https://github.com/eclipse/xtext-core/issues/1467">xtext-core#1467</a></li>
+ <li><code>Internal&lt;dslName&gt;Parser.java</code> file in the <strong>runtime</strong> module - <a href="https://github.com/eclipse/xtext-core/issues/1467">xtext-core#1467</a></li>
+ <li><code>&lt;dslName&gt;GrammarAccess.java</code> file in the <strong>runtime</strong> module - <a href="https://github.com/eclipse/xtext-core/issues/269">xtext-core#269</a></li>
+ <li><code>Partial&lt;dslName&gt;ContentAssistParser.java</code> file in the <strong>ide</strong> module - <a href="https://github.com/eclipse/xtext-core/issues/1418">xtext-core#1418</a></li>
+</ul>
+
+<p>We encourage you to regenerate your languages with the latest Xtext version. Usually you do not recognize any changes, unless you check-in the <code>src-gen</code> folders in a version control system.</p>
+
+<h2 id="eclipse-integration">Eclipse Integration</h2>
+
+<h2 id="upgrades">Upgrades</h2>
+
+<ul>
+ <li>Xtext 2.22 requires ASM 8.0.1 (updated from 7.2.0).</li>
+ <li>Maven Tycho was updated to version 1.7.0.</li>
+ <li>MWE(2) was updated to 2.11.3/1.5.3.</li>
+</ul>
+
+<h2 id="removals">Removals</h2>
+
+<ul>
+ <li>Xtext no longer has a direct dependency to ICU4J. If you use ICU4J in your codebase you should also consider to get rid of this dependencies as it will no longer be supported by Eclipse (Platform).</li>
+ <li>As announced in the 2.21 Release the deprecated API in the LSP area was removed.</li>
+ <li>We also removed the outdated leftovers of IDEA Support in <code>org.eclipse.xtext.xtext.generator</code>.</li>
+</ul>
+
+<h2 id="deprecations">Deprecations</h2>
+
+<ul>
+ <li><code>IXtext2EcorePostProcessor</code> &amp; <code>XtendXtext2EcorePostProcessor</code> &amp; <code>ProjectAwareXtendXtext2EcorePostProcessor</code> were deprecated as they depend on old Xpand/Xtend(1). As already announced in the <a href="2020-03-03-version-2-21-0.md">2.21 release notes</a> you should avoid depending on the old Xpand based <code>org.eclipse.xtext.generator</code> as well as on Xtend(1) based postprocessing. So if you have an <code>.ext</code> file right next to your <code>.xtext</code> file or subclass the interface it’s about time to switch to a manually maintained Ecore model.</li>
+</ul>
+
+<h2 id="credits">Credits</h2>
+
+<p>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 <a href="https://github.com/eclipse/xtext#repositories">all repositories</a> except <a href="https://github.com/eclipse/xtext-xtend">xtext-xtend</a>):</p>
+
+<ul>
+ <li>Christian Dietrich (itemis)</li>
+ <li>Tamas Miklossy (itemis)</li>
+ <li>Nico Prediger (itemis)</li>
+ <li>Sebastian Zarnekow (independent)</li>
+ <li>Karsten Thoms (Karakun)</li>
+ <li>Neeraj Bhusare (Zafin)</li>
+ <li>Arne Deutsch (itemis)</li>
+ <li>Jan Koehnlein (TypeFox)</li>
+ <li>George Suaridze (1C LLC) <img src="https://img.shields.io/badge/-first%20time%20contributor-green.svg" alt="" /></li>
+ <li>Mathias Rieder (Bachmann)</li>
+ <li>Mikael Barbero (Eclipse Foundation)</li>
+ <li>Titouan Vervack (Sigasi)</li>
+</ul>
+
+<h2 id="fixed-issues">Fixed Issues</h2>
+
+<p>As in every release cycle we were eagerly hunting down bugs, and reviewed and integrated plenty of contributions. For further details please refer to the following lists:</p>
+
+<ul>
+ <li>
+ <p><a href="https://github.com/search?utf8=%E2%9C%93&amp;q=is%3Aissue+milestone%3ARelease_2.22+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;type=Issues&amp;ref=searchresults">Fixed GitHub issues</a></p>
+ </li>
+ <li>
+ <p><a href="https://github.com/search?utf8=%E2%9C%93&amp;q=is%3Apr+milestone%3ARelease_2.22+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;type=Issues&amp;ref=searchresults">Closed Pull Requests</a></p>
+ </li>
+ <li>
+ <p><a href="https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&amp;bug_status=VERIFIED&amp;bug_status=CLOSED&amp;classification=Modeling&amp;classification=Tools&amp;columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ckeywords&amp;f0=OP&amp;f1=OP&amp;f3=CP&amp;f4=CP&amp;known_name=Xtext%202.22&amp;list_id=16618269&amp;product=TMF&amp;product=Xtend&amp;query_based_on=Xtext%202.22&amp;query_format=advanced&amp;status_whiteboard=v2.22&amp;status_whiteboard_type=allwordssubstr">Fixed Eclipse Bugzilla tickets</a></p>
+ </li>
+</ul>
+</description>
+ <pubDate>Tue, 02 Jun 2020 00:00:00 +0000</pubDate>
+ <link>http://xtext.org/Xtext/releasenotes/2020/06/02/version-2-22-0.html</link>
+ <guid isPermaLink="true">http://xtext.org/Xtext/releasenotes/2020/06/02/version-2-22-0.html</guid>
+
+
+ <category>releasenotes</category>
+
+ </item>
+
+ <item>
<title>Xtext 2.21.0 Release Notes</title>
<description><p>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.</p>
@@ -1089,230 +1183,5 @@
</item>
- <item>
- <title>Xtext 2.13.0 Release Notes</title>
- <description><h2 id="language-server-support">Language Server Support</h2>
-
-<h3 id="eclipse-new-project-wizard-language-server-build">Eclipse New Project Wizard: Language Server Build</h3>
-
-<p>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:</p>
-
-<ul>
- <li><strong>Regular</strong>: 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.</li>
- <li><strong>Fat Jar</strong>: The language server is packaged in a single executable jar.</li>
-</ul>
-
-<p>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</p>
-
-<p><img src="/Xtext/images/releasenotes/2_13_project-wizard-ls.png" alt="" /></p>
-
-<h2 id="eclipse-integration">Eclipse Integration</h2>
-
-<h3 id="configuration-error-detection">Configuration Error Detection</h3>
-
-<p>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.</p>
-
-<p>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.</p>
-
-<p>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.</p>
-
-<h3 id="multi-quickfixes">Multi-Quickfixes</h3>
-
-<p>These are quickfixes that allow to be applied to multiple markers at once.</p>
-
-<p>TBD</p>
-
-<h3 id="better-cancellation-in-refactorings">Better Cancellation in Refactorings</h3>
-
-<p>You can how hit the cancel dialog in refactorings and it will actually cancel at the next opportunity and not at the end only.</p>
-
-<h3 id="content-type-descriptor">Content Type Descriptor</h3>
-
-<p>Xtext UI projects provide a Content Type Descriptor by contributing to the <a href="https://help.eclipse.org/oxygen/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fruntime_content_contributing.htm"><code>org.eclipse.core.contenttype.contentTypes</code> extension point</a> to the <code>plugin.xml</code> 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. (<a href="https://github.com/eclipse/xtext-eclipse/issues/379">xtext-eclipse/issues/379</a>)</p>
-
-<pre><code>&lt;extension point="org.eclipse.core.contenttype.contentTypes"&gt;
- &lt;content-type
- base-type="org.eclipse.core.runtime.text"
- file-extensions="mydsl"
- id="org.eclipse.xtext.mydsl.MyDSL.contenttype"
- name="MyDSL File"
- priority="normal"&gt;
- &lt;/content-type&gt;
-&lt;/extension&gt;
-</code></pre>
-
-<h2 id="new-api">New API</h2>
-
-<h3 id="emf-model-manipulation-api-incubating">EMF Model Manipulation API (incubating)</h3>
-
-<p>The <code>IChangeSerializer</code> 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 <code>XtextDocument.modify()</code> approach:</p>
-
-<ul>
- <li>Direct integration with the formatter, such that changes are automatically nicely formatted.</li>
- <li>Minimum text region changes resulting in less noise.</li>
- <li>Many points to hook into, e.g. for automatic update of an import section.</li>
- <li>More ways to optimize for a specific language and to tune performance.</li>
- <li>Independence from Eclipse-UI concepts like the <code>Document</code>. This makes it reusable in languages server implementations.</li>
-</ul>
-
-<p>You can use the <code>IChangeSerializer</code> 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.</p>
-
-<p>Nevertheless, we have added the following new features based on it:</p>
-
-<h3 id="rename-participants-for-eclipse-file-operations">Rename Participants for Eclipse File Operations</h3>
-
-<p>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 <code>IChangeSerializer</code> we have implemented some generic file refactoring participants. You will get notified of such changes to react appropriately by registering your own <code>IResourceRelocationStrategy</code>.</p>
-
-<pre><code>&lt;extension point="org.eclipse.xtext.ui.resourceRelocationStrategy"&gt;
- &lt;strategy class="mydsl.MydslExecutableExtensionFactory:mydsl.MydslResourceRelocationStrategy"&gt;
- &lt;/strategy&gt;
-&lt;/extension&gt;
-</code></pre>
-
-<h3 id="alternative-rename-refactoring-for-xtext">Alternative Rename Refactoring for Xtext</h3>
-
-<p>By enabling <code>useChangeSerializer</code> flag in the workflow of your language</p>
-<pre><code>Workflow {
- component = XtextGenerator {
- ...
- language = StandardLanguage {
- ...
- renameRefactoring = {
- useChangeSerializer = true
- ...
-</code></pre>
-<p>you will use an new, alternative rename refactoring for Eclipse based on the <code>IChangeSerializer</code>. This flag will also generate the binding for the <code>IRenameService</code> and thereby enable rename refactoring on your language server.</p>
-
-<h3 id="xbase-library-orgeclipsextextxbaselib">Xbase Library (<code>org.eclipse.xtext.xbase.lib</code>)</h3>
-
-<h4 id="no-arg-overloads-to-all-mutable-collection-literals">No-arg overloads to all mutable collection literals</h4>
-
-<p>Class <code>CollectionLiterals</code> was extended by no-arg methods for all mutable collection literals:</p>
-<ul>
- <li><code>newArrayList()</code></li>
- <li><code>newHashMap()</code></li>
- <li><code>newHashSet()</code></li>
- <li><code>newLinkedHashMap()</code></li>
- <li><code>newLinkedHashSet()</code></li>
- <li><code>newLinkedList()</code></li>
-</ul>
-
-<p>Xtext’s code base was refactored to use these methods where appropriate. As a consequence Xtext requires at least version 2.13 of <code>org.eclipse.xtext.xbase.lib</code>. Therefore bundle manifests were refactored to constraint the library bundle’s lower version. New projects will automatically add the version constraint to manifests.</p>
-
-<h4 id="flatmap-extension-method">flatMap extension method</h4>
-
-<p>A new convenience method <code>flatMap</code> has been added to <code>IterableExtensions</code> and <code>IteratorExtensions</code>, which combines <code>map</code> and <code>flatten</code>.</p>
-
-<pre><code>@FinalFieldsConstructor
-@Accessors
-class Planet {
- final String name
- final List&lt;Moon&gt; moons
-}
-
-@FinalFieldsConstructor
-@Accessors
-class Moon {
- final String name
-}
-
-
-class Planets {
- def static void main (String[] args) {
-
- val Iterable&lt;Planet&gt; planets = #[
- new Planet("Earth", #[new Moon ("Moon")]),
- new Planet("Mars", #[new Moon ("Phobos"), new Moon("Deimos")])
- ]
-
- val moonNames_old = planets.map[moons].flatten.map[name]
- val moonNames_new = planets.flatMap[moons].map[name]
- }
-}
-</code></pre>
-
-<h2 id="tracing">Tracing</h2>
-
-<p>Tracing can now be used for debugging in generated Java code as well. The <code>@Traced</code> annotation now takes optionally a <code>useForDebugging=true</code>. The <code>@TracedAccessors</code> are now adds to the <code>._&lt;feature&gt;()</code> extension method a <code>._&lt;feature&gt;(useForDebugging)</code> extension method.</p>
-
-<h2 id="refactoring">Refactoring</h2>
-
-<h3 id="jdt-dependency-reduction">JDT Dependency Reduction</h3>
-
-<p>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 (<code>NoClassDefFoundError</code>). Dependencies in the following bundles have been resolved:</p>
-
-<ul>
- <li><code>org.eclipse.xtext.builder</code> (<a href="https://github.com/eclipse/xtext-eclipse/issues/386">issue#386</a>)</li>
- <li><code>org.eclipse.xtext.xbase.ui</code> (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=509630">bug#509630</a>)</li>
-</ul>
-
-<p>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. (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=525462">bug#525462</a>)</p>
-
-<h3 id="improved-support-for-indentation-based-languages">Improved Support for Indentation Based Languages</h3>
-
-<p>Token placement for INDENT / DEDENT tokens have been improved. This improves content assist for indentation based languages. (<a href="https://github.com/eclipse/xtext-core/pull/366">issue#366</a>)</p>
-
-<h3 id="new-generator-infrastructure">New Generator Infrastructure</h3>
-
-<p>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.</p>
-
-<h2 id="an-eye-on-quality">An Eye on Quality</h2>
-
-<p>With every release we are working hard on fixing as many bugs as possible. Besides our Bugtrackers Eclipse Bugzilla and GitHub Issues the <a href="https://www.codetrails.com/error-analytics/">Automatic Error Reporting System</a> 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.</p>
-
-<p>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.</p>
-
-<p>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.</p>
-
-<p><img src="/Xtext/images/releasenotes/2_13_aeri_problem_status.png" alt="" /><br />
-<img src="/Xtext/images/releasenotes/2_13_aeri_problem_resolution.png" alt="" /><br />
-<img src="/Xtext/images/releasenotes/2_13_aeri_incidents_timeline.png" alt="" /></p>
-
-<h2 id="improved-developer-contribution-support">Improved Developer Contribution Support</h2>
-
-<p>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 <a href="https://www.eclipse.org/downloads/">Eclipse Installer</a>, 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.</p>
-
-<h3 id="execution-environment">Execution Environment</h3>
-
-<p>Minimal requirements are:</p>
-<ul>
- <li>Java 8</li>
- <li>Eclipse Luna</li>
- <li>EMF 2.10</li>
- <li>Guice 3.0</li>
-</ul>
-
-<p>Xtext has been tested also on Eclipse Oxygen.1a and Eclipse Photon M2.</p>
-
-<h2 id="some-words-on-java-9">Some words on Java 9</h2>
-
-<p>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 <code>org.objectweb.asm</code> 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 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=526209">bug</a> 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.</p>
-
-<h2 id="fixed-issues">Fixed Issues</h2>
-
-<p>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:</p>
-
-<ul>
- <li>
- <p><a href="https://github.com/search?utf8=%E2%9C%93&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;type=Issues&amp;ref=searchresults">Fixed GitHub issues</a></p>
- </li>
- <li>
- <p><a href="https://github.com/search?utf8=%E2%9C%93&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;type=Issues&amp;ref=searchresults">Closed Pull Requests</a></p>
- </li>
- <li>
- <p><a href="https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&amp;bug_status=VERIFIED&amp;bug_status=CLOSED&amp;classification=Modeling&amp;classification=Tools&amp;columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ckeywords&amp;f0=OP&amp;f1=OP&amp;f3=CP&amp;f4=CP&amp;known_name=Xtext%202.13&amp;list_id=16618269&amp;product=TMF&amp;product=Xtend&amp;query_based_on=Xtext%202.13&amp;query_format=advanced&amp;status_whiteboard=v2.13&amp;status_whiteboard_type=allwordssubstr">Fixed Eclipse Bugzilla tickets</a></p>
- </li>
-</ul>
-
-</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>
diff --git a/releasenotes.html b/releasenotes.html
index d90f9bb..958aaa8 100644
--- a/releasenotes.html
+++ b/releasenotes.html
@@ -134,6 +134,8 @@
<h3>Table of Contents</h3>
<ul>
+ <li><p><a href="#/releasenotes/2020/06/02/version-2-22-0">Xtext 2.22.0 Release Notes — Jun 2, 2020</a></p>
+
<li><p><a href="#/releasenotes/2020/03/03/version-2-21-0">Xtext 2.21.0 Release Notes — Mar 3, 2020</a></p>
<li><p><a href="#/releasenotes/2019/12/03/version-2-20-0">Xtext 2.20.0 Release Notes — Dec 3, 2019</a></p>
@@ -152,12 +154,99 @@
<li><p><a href="#/releasenotes/2018/05/23/version-2-14-0">Xtext 2.14.0 Release Notes — May 23, 2018</a></p>
- <li><p><a href="#/releasenotes/2017/10/20/version-2-13-0">Xtext 2.13.0 Release Notes — Oct 20, 2017</a></p>
-
</ul>
</div>
<hr/>
+ <section id="/releasenotes/2020/06/02/version-2-22-0">
+ <h1>Xtext 2.22.0 Release Notes<small> Jun 2, 2020</small></h1>
+ <br/>
+ <p>Xtext 2.22.0 is mainly a maintenance release.</p>
+
+<h2 id="call-to-action-secure-the-future-maintenance-of-xtext">Call to Action: Secure the future maintenance of Xtext</h2>
+
+<p>As you might have recognized, the number of people contributing to Xtext on a regular basis has declined over the past years and so has the number of contributions. At the same time the amount of work for basic maintenance has stayed the same or even increased with the new release cadence of Java and the Eclipse simultaneous release. Briefly: The future maintenance of Xtext is at risk. If you care, please join the discussion in <a href="https://github.com/eclipse/xtext/issues/1721">https://github.com/eclipse/xtext/issues/1721</a>.</p>
+
+<h2 id="documentation">Documentation</h2>
+
+<p>The <a href="https://www.eclipse.org/Xtext/community.html">Xtext community website</a> and the <a href="https://www.eclipse.org/Xtext/documentation/index.html">Xtext documentation website</a> have been updated. New Xtext-based projects have been added, some editor features and the Unit testing / UI testing capabilities have been documented and the embedded code snippets have been updated as well.</p>
+
+<p>We further enhanced the <a href="https://github.com/eclipse/xtext/tree/master/dev-doc">Xtext Developer Documentation</a> to enable the community to easily contribute to Xtext.</p>
+
+<h2 id="code-generation-improvements">Code Generation improvements</h2>
+<p>This release contains some fixes to improve the generated code in the <code>src-gen</code> folders. The following files are affected:</p>
+
+<ul>
+ <li><code>Internal<dslName>.g</code> file in the <strong>runtime</strong> module - <a href="https://github.com/eclipse/xtext-core/issues/1467">xtext-core#1467</a></li>
+ <li><code>Internal<dslName>Parser.java</code> file in the <strong>runtime</strong> module - <a href="https://github.com/eclipse/xtext-core/issues/1467">xtext-core#1467</a></li>
+ <li><code><dslName>GrammarAccess.java</code> file in the <strong>runtime</strong> module - <a href="https://github.com/eclipse/xtext-core/issues/269">xtext-core#269</a></li>
+ <li><code>Partial<dslName>ContentAssistParser.java</code> file in the <strong>ide</strong> module - <a href="https://github.com/eclipse/xtext-core/issues/1418">xtext-core#1418</a></li>
+</ul>
+
+<p>We encourage you to regenerate your languages with the latest Xtext version. Usually you do not recognize any changes, unless you check-in the <code>src-gen</code> folders in a version control system.</p>
+
+<h2 id="eclipse-integration">Eclipse Integration</h2>
+
+<h2 id="upgrades">Upgrades</h2>
+
+<ul>
+ <li>Xtext 2.22 requires ASM 8.0.1 (updated from 7.2.0).</li>
+ <li>Maven Tycho was updated to version 1.7.0.</li>
+ <li>MWE(2) was updated to 2.11.3/1.5.3.</li>
+</ul>
+
+<h2 id="removals">Removals</h2>
+
+<ul>
+ <li>Xtext no longer has a direct dependency to ICU4J. If you use ICU4J in your codebase you should also consider to get rid of this dependencies as it will no longer be supported by Eclipse (Platform).</li>
+ <li>As announced in the 2.21 Release the deprecated API in the LSP area was removed.</li>
+ <li>We also removed the outdated leftovers of IDEA Support in <code>org.eclipse.xtext.xtext.generator</code>.</li>
+</ul>
+
+<h2 id="deprecations">Deprecations</h2>
+
+<ul>
+ <li><code>IXtext2EcorePostProcessor</code> & <code>XtendXtext2EcorePostProcessor</code> & <code>ProjectAwareXtendXtext2EcorePostProcessor</code> were deprecated as they depend on old Xpand/Xtend(1). As already announced in the <a href="2020-03-03-version-2-21-0.md">2.21 release notes</a> you should avoid depending on the old Xpand based <code>org.eclipse.xtext.generator</code> as well as on Xtend(1) based postprocessing. So if you have an <code>.ext</code> file right next to your <code>.xtext</code> file or subclass the interface it’s about time to switch to a manually maintained Ecore model.</li>
+</ul>
+
+<h2 id="credits">Credits</h2>
+
+<p>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 <a href="https://github.com/eclipse/xtext#repositories">all repositories</a> except <a href="https://github.com/eclipse/xtext-xtend">xtext-xtend</a>):</p>
+
+<ul>
+ <li>Christian Dietrich (itemis)</li>
+ <li>Tamas Miklossy (itemis)</li>
+ <li>Nico Prediger (itemis)</li>
+ <li>Sebastian Zarnekow (independent)</li>
+ <li>Karsten Thoms (Karakun)</li>
+ <li>Neeraj Bhusare (Zafin)</li>
+ <li>Arne Deutsch (itemis)</li>
+ <li>Jan Koehnlein (TypeFox)</li>
+ <li>George Suaridze (1C LLC) <img src="https://img.shields.io/badge/-first%20time%20contributor-green.svg" alt="" /></li>
+ <li>Mathias Rieder (Bachmann)</li>
+ <li>Mikael Barbero (Eclipse Foundation)</li>
+ <li>Titouan Vervack (Sigasi)</li>
+</ul>
+
+<h2 id="fixed-issues">Fixed Issues</h2>
+
+<p>As in every release cycle we were eagerly hunting down bugs, and reviewed and integrated plenty of contributions. For further details please refer to the following lists:</p>
+
+<ul>
+ <li>
+ <p><a href="https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+milestone%3ARelease_2.22+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&type=Issues&ref=searchresults">Fixed GitHub issues</a></p>
+ </li>
+ <li>
+ <p><a href="https://github.com/search?utf8=%E2%9C%93&q=is%3Apr+milestone%3ARelease_2.22+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&type=Issues&ref=searchresults">Closed Pull Requests</a></p>
+ </li>
+ <li>
+ <p><a href="https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&classification=Modeling&classification=Tools&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ckeywords&f0=OP&f1=OP&f3=CP&f4=CP&known_name=Xtext%202.22&list_id=16618269&product=TMF&product=Xtend&query_based_on=Xtext%202.22&query_format=advanced&status_whiteboard=v2.22&status_whiteboard_type=allwordssubstr">Fixed Eclipse Bugzilla tickets</a></p>
+ </li>
+</ul>
+
+ </section>
+
+ <hr/>
<section id="/releasenotes/2020/03/03/version-2-21-0">
<h1>Xtext 2.21.0 Release Notes<small> Mar 3, 2020</small></h1>
<br/>
@@ -1191,226 +1280,6 @@
</section>
- <hr/>
- <section id="/releasenotes/2017/10/20/version-2-13-0">
- <h1>Xtext 2.13.0 Release Notes<small> Oct 20, 2017</small></h1>
- <br/>
- <h2 id="language-server-support">Language Server Support</h2>
-
-<h3 id="eclipse-new-project-wizard-language-server-build">Eclipse New Project Wizard: Language Server Build</h3>
-
-<p>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:</p>
-
-<ul>
- <li><strong>Regular</strong>: 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.</li>
- <li><strong>Fat Jar</strong>: The language server is packaged in a single executable jar.</li>
-</ul>
-
-<p>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</p>
-
-<p><img src="/Xtext/images/releasenotes/2_13_project-wizard-ls.png" alt="" /></p>
-
-<h2 id="eclipse-integration">Eclipse Integration</h2>
-
-<h3 id="configuration-error-detection">Configuration Error Detection</h3>
-
-<p>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.</p>
-
-<p>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.</p>
-
-<p>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.</p>
-
-<h3 id="multi-quickfixes">Multi-Quickfixes</h3>
-
-<p>These are quickfixes that allow to be applied to multiple markers at once.</p>
-
-<p>TBD</p>
-
-<h3 id="better-cancellation-in-refactorings">Better Cancellation in Refactorings</h3>
-
-<p>You can how hit the cancel dialog in refactorings and it will actually cancel at the next opportunity and not at the end only.</p>
-
-<h3 id="content-type-descriptor">Content Type Descriptor</h3>
-
-<p>Xtext UI projects provide a Content Type Descriptor by contributing to the <a href="https://help.eclipse.org/oxygen/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fruntime_content_contributing.htm"><code>org.eclipse.core.contenttype.contentTypes</code> extension point</a> to the <code>plugin.xml</code> 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. (<a href="https://github.com/eclipse/xtext-eclipse/issues/379">xtext-eclipse/issues/379</a>)</p>
-
-<pre><code><extension point="org.eclipse.core.contenttype.contentTypes">
- <content-type
- base-type="org.eclipse.core.runtime.text"
- file-extensions="mydsl"
- id="org.eclipse.xtext.mydsl.MyDSL.contenttype"
- name="MyDSL File"
- priority="normal">
- </content-type>
-</extension>
-</code></pre>
-
-<h2 id="new-api">New API</h2>
-
-<h3 id="emf-model-manipulation-api-incubating">EMF Model Manipulation API (incubating)</h3>
-
-<p>The <code>IChangeSerializer</code> 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 <code>XtextDocument.modify()</code> approach:</p>
-
-<ul>
- <li>Direct integration with the formatter, such that changes are automatically nicely formatted.</li>
- <li>Minimum text region changes resulting in less noise.</li>
- <li>Many points to hook into, e.g. for automatic update of an import section.</li>
- <li>More ways to optimize for a specific language and to tune performance.</li>
- <li>Independence from Eclipse-UI concepts like the <code>Document</code>. This makes it reusable in languages server implementations.</li>
-</ul>
-
-<p>You can use the <code>IChangeSerializer</code> 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.</p>
-
-<p>Nevertheless, we have added the following new features based on it:</p>
-
-<h3 id="rename-participants-for-eclipse-file-operations">Rename Participants for Eclipse File Operations</h3>
-
-<p>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 <code>IChangeSerializer</code> we have implemented some generic file refactoring participants. You will get notified of such changes to react appropriately by registering your own <code>IResourceRelocationStrategy</code>.</p>
-
-<pre><code><extension point="org.eclipse.xtext.ui.resourceRelocationStrategy">
- <strategy class="mydsl.MydslExecutableExtensionFactory:mydsl.MydslResourceRelocationStrategy">
- </strategy>
-</extension>
-</code></pre>
-
-<h3 id="alternative-rename-refactoring-for-xtext">Alternative Rename Refactoring for Xtext</h3>
-
-<p>By enabling <code>useChangeSerializer</code> flag in the workflow of your language</p>
-<pre><code>Workflow {
- component = XtextGenerator {
- ...
- language = StandardLanguage {
- ...
- renameRefactoring = {
- useChangeSerializer = true
- ...
-</code></pre>
-<p>you will use an new, alternative rename refactoring for Eclipse based on the <code>IChangeSerializer</code>. This flag will also generate the binding for the <code>IRenameService</code> and thereby enable rename refactoring on your language server.</p>
-
-<h3 id="xbase-library-orgeclipsextextxbaselib">Xbase Library (<code>org.eclipse.xtext.xbase.lib</code>)</h3>
-
-<h4 id="no-arg-overloads-to-all-mutable-collection-literals">No-arg overloads to all mutable collection literals</h4>
-
-<p>Class <code>CollectionLiterals</code> was extended by no-arg methods for all mutable collection literals:</p>
-<ul>
- <li><code>newArrayList()</code></li>
- <li><code>newHashMap()</code></li>
- <li><code>newHashSet()</code></li>
- <li><code>newLinkedHashMap()</code></li>
- <li><code>newLinkedHashSet()</code></li>
- <li><code>newLinkedList()</code></li>
-</ul>
-
-<p>Xtext’s code base was refactored to use these methods where appropriate. As a consequence Xtext requires at least version 2.13 of <code>org.eclipse.xtext.xbase.lib</code>. Therefore bundle manifests were refactored to constraint the library bundle’s lower version. New projects will automatically add the version constraint to manifests.</p>
-
-<h4 id="flatmap-extension-method">flatMap extension method</h4>
-
-<p>A new convenience method <code>flatMap</code> has been added to <code>IterableExtensions</code> and <code>IteratorExtensions</code>, which combines <code>map</code> and <code>flatten</code>.</p>
-
-<pre><code>@FinalFieldsConstructor
-@Accessors
-class Planet {
- final String name
- final List<Moon> moons
-}
-
-@FinalFieldsConstructor
-@Accessors
-class Moon {
- final String name
-}
-
-
-class Planets {
- def static void main (String[] args) {
-
- val Iterable<Planet> planets = #[
- new Planet("Earth", #[new Moon ("Moon")]),
- new Planet("Mars", #[new Moon ("Phobos"), new Moon("Deimos")])
- ]
-
- val moonNames_old = planets.map[moons].flatten.map[name]
- val moonNames_new = planets.flatMap[moons].map[name]
- }
-}
-</code></pre>
-
-<h2 id="tracing">Tracing</h2>
-
-<p>Tracing can now be used for debugging in generated Java code as well. The <code>@Traced</code> annotation now takes optionally a <code>useForDebugging=true</code>. The <code>@TracedAccessors</code> are now adds to the <code>._<feature>()</code> extension method a <code>._<feature>(useForDebugging)</code> extension method.</p>
-
-<h2 id="refactoring">Refactoring</h2>
-
-<h3 id="jdt-dependency-reduction">JDT Dependency Reduction</h3>
-
-<p>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 (<code>NoClassDefFoundError</code>). Dependencies in the following bundles have been resolved:</p>
-
-<ul>
- <li><code>org.eclipse.xtext.builder</code> (<a href="https://github.com/eclipse/xtext-eclipse/issues/386">issue#386</a>)</li>
- <li><code>org.eclipse.xtext.xbase.ui</code> (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=509630">bug#509630</a>)</li>
-</ul>
-
-<p>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. (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=525462">bug#525462</a>)</p>
-
-<h3 id="improved-support-for-indentation-based-languages">Improved Support for Indentation Based Languages</h3>
-
-<p>Token placement for INDENT / DEDENT tokens have been improved. This improves content assist for indentation based languages. (<a href="https://github.com/eclipse/xtext-core/pull/366">issue#366</a>)</p>
-
-<h3 id="new-generator-infrastructure">New Generator Infrastructure</h3>
-
-<p>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.</p>
-
-<h2 id="an-eye-on-quality">An Eye on Quality</h2>
-
-<p>With every release we are working hard on fixing as many bugs as possible. Besides our Bugtrackers Eclipse Bugzilla and GitHub Issues the <a href="https://www.codetrails.com/error-analytics/">Automatic Error Reporting System</a> 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.</p>
-
-<p>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.</p>
-
-<p>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.</p>
-
-<p><img src="/Xtext/images/releasenotes/2_13_aeri_problem_status.png" alt="" /><br />
-<img src="/Xtext/images/releasenotes/2_13_aeri_problem_resolution.png" alt="" /><br />
-<img src="/Xtext/images/releasenotes/2_13_aeri_incidents_timeline.png" alt="" /></p>
-
-<h2 id="improved-developer-contribution-support">Improved Developer Contribution Support</h2>
-
-<p>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 <a href="https://www.eclipse.org/downloads/">Eclipse Installer</a>, 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.</p>
-
-<h3 id="execution-environment">Execution Environment</h3>
-
-<p>Minimal requirements are:</p>
-<ul>
- <li>Java 8</li>
- <li>Eclipse Luna</li>
- <li>EMF 2.10</li>
- <li>Guice 3.0</li>
-</ul>
-
-<p>Xtext has been tested also on Eclipse Oxygen.1a and Eclipse Photon M2.</p>
-
-<h2 id="some-words-on-java-9">Some words on Java 9</h2>
-
-<p>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 <code>org.objectweb.asm</code> 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 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=526209">bug</a> 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.</p>
-
-<h2 id="fixed-issues">Fixed Issues</h2>
-
-<p>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:</p>
-
-<ul>
- <li>
- <p><a href="https://github.com/search?utf8=%E2%9C%93&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&type=Issues&ref=searchresults">Fixed GitHub issues</a></p>
- </li>
- <li>
- <p><a href="https://github.com/search?utf8=%E2%9C%93&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&type=Issues&ref=searchresults">Closed Pull Requests</a></p>
- </li>
- <li>
- <p><a href="https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&classification=Modeling&classification=Tools&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ckeywords&f0=OP&f1=OP&f3=CP&f4=CP&known_name=Xtext%202.13&list_id=16618269&product=TMF&product=Xtend&query_based_on=Xtext%202.13&query_format=advanced&status_whiteboard=v2.13&status_whiteboard_type=allwordssubstr">Fixed Eclipse Bugzilla tickets</a></p>
- </li>
-</ul>
-
-
- </section>
-
</div>
</div>
diff --git a/releasenotes/2020/06/02/version-2-22-0.html b/releasenotes/2020/06/02/version-2-22-0.html
new file mode 100644
index 0000000..520ccd9
--- /dev/null
+++ b/releasenotes/2020/06/02/version-2-22-0.html
@@ -0,0 +1,318 @@
+<!DOCTYPE html>
+<html>
+
+ <head>
+ <meta charset="UTF-8">
+ <title>Xtext - Xtext 2.22.0 Release Notes</title>
+
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+ <meta name="description"
+ content="The website of Eclipse Xtext, an open-source framework for development of programming languages and domain-specific languages">
+ <meta name="author" content="Sven Efftinge">
+ <meta name="author" content="Miro Spoenemann">
+ <!-- styles -->
+ <!-- Le HTML5 shim, for IE6-8 support of HTML5 elements -->
+ <!--[if lt IE 9]>
+ <script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
+ <![endif]-->
+
+ <!-- Le fav and touch icons -->
+ <link rel="shortcut icon" href="/Xtext/images/favicon.png">
+
+ <link href="/Xtext/css/bootstrap.css" rel="stylesheet" type='text/css'>
+ <link href="/Xtext/css/bootstrap-responsive.css" rel="stylesheet" type='text/css'>
+ <link href="/Xtext/css/shield-responsive.css" rel="stylesheet" type='text/css'>
+ <link href='/Xtext/css/fonts.css' rel='stylesheet' type='text/css'>
+ <link href="/Xtext/css/prettyPhoto.css" rel="stylesheet" media="screen" type='text/css'>
+ <link href="/Xtext/css/prettify.css" type="text/css" rel="stylesheet"/>
+ <link href="/Xtext/css/style.css" rel="stylesheet" type='text/css'>
+ <!-- cover flow -->
+ <link href="/Xtext/css/coverflow.css" rel="stylesheet" type='text/css'>
+ <!--[if lt IE 9]>
+ <link href="/css/iebugs.css" rel="stylesheet" type='text/css'>
+ <![endif]-->
+
+ <!-- BEGIN Cookie Consent
+ <link rel="stylesheet" type="text/css" href="//cdnjs.cloudflare.com/ajax/libs/cookieconsent2/3.0.3/cookieconsent.min.css" />
+ <script src="//cdnjs.cloudflare.com/ajax/libs/cookieconsent2/3.0.3/cookieconsent.min.js"></script>
+ <script>
+ window.addEventListener("load", function(){
+ window.cookieconsent.initialise({
+ "palette": {
+ "popup": {
+ "background": "#000"
+ },
+ "button": {
+ "background": "#f1d600"
+ }
+ },
+ "theme": "edgeless",
+ "type": "opt-in",
+ onInitialise: function (status) {
+ var type = this.options.type;
+ var didConsent = this.hasConsented();
+ if (type == 'opt-in' && didConsent) {
+ // TODO: enable cookies
+ }
+ if (type == 'opt-out' && !didConsent) {
+ // TODO: disable cookies
+ }
+ },
+ onStatusChange: function(status, chosenBefore) {
+ var type = this.options.type;
+ var didConsent = this.hasConsented();
+ if (type == 'opt-in' && didConsent) {
+ // TODO: enable cookies
+ }
+ if (type == 'opt-out' && !didConsent) {
+ // TODO: disable cookies
+ }
+ },
+ onRevokeChoice: function() {
+ var type = this.options.type;
+ if (type == 'opt-in') {
+ // TODO: disable cookies
+ }
+ if (type == 'opt-out') {
+ // TODO: enable cookies
+ }
+ },
+ "content": {
+ "href": "http://www.eclipse.org/legal/privacy.php"
+ }
+ })});
+ </script>
+ END Cookie Consent -->
+</head>
+
+
+ <body>
+
+ <header class="site-header">
+
+ <!-- Navbar -->
+ <div class="navbar navbar-fixed-top">
+ <div class="navbar-inner">
+ <div class="container">
+ <a class="btn btn-navbar" data-toggle="collapse"
+ data-target=".nav-collapse"> <span class="icon-bar"></span> <span
+ class="icon-bar"></span> <span class="icon-bar"></span>
+ </a> <a class="brand" href="/Xtext/index.html"></a>
+ <div class="nav-collapse collapse" style="height: 0px;">
+ <ul class="nav">
+ <!--li ><a href="/Xtext/news.html">News</a></li-->
+ <li ><a href="/Xtext/download.html">Download</a></li>
+ <li ><a href="/Xtext/documentation/index.html">Documentation</a></li>
+ <li ><a href="/Xtext/community.html">Community</a></li>
+ <li class="dropdown">
+ <a class="dropdown-toggle" data-toggle="dropdown" href="#">Support & Trainings<span class="caret"></span></a>
+ <ul class="dropdown-menu">
+ <li><a href="https://www.itemis.com/en/xtext/support-and-team/" target="_blank">itemis</a></li>
+ <li><a href="https://typefox.io/trainings-2" target="_blank">TypeFox</a></li>
+ </ul>
+ </li>
+ <li ><a href="http://xtend-lang.org">Xtend</a></li>
+ </ul>
+ <!--div class="nav pull-right">
+ <li ><a><iframe src="https://ghbtns.com/github-btn.html?user=eclipse&repo=xtext&type=star&count=true" frameborder="0" scrolling="0" width="170px" height="20px"></iframe></a></li>
+ </div-->
+ </div>
+ <!--/.nav-collapse -->
+ </div>
+ </div>
+ </div>
+ <!-- Navbar End -->
+
+</header>
+
+
+ <div class="page-content">
+ <div class="wrapper">
+ <div id="page">
+ <div class="inner">
+ <br/><br/>
+ <div id="maincontainer" class="container">
+ <div class="span8 offset1">
+ <h1>Xtext 2.22.0 Release Notes</h1>
+ <h4>Jun 2, 2020</h4>
+ <br/>
+ <p>Xtext 2.22.0 is mainly a maintenance release.</p>
+
+<h2 id="call-to-action-secure-the-future-maintenance-of-xtext">Call to Action: Secure the future maintenance of Xtext</h2>
+
+<p>As you might have recognized, the number of people contributing to Xtext on a regular basis has declined over the past years and so has the number of contributions. At the same time the amount of work for basic maintenance has stayed the same or even increased with the new release cadence of Java and the Eclipse simultaneous release. Briefly: The future maintenance of Xtext is at risk. If you care, please join the discussion in <a href="https://github.com/eclipse/xtext/issues/1721">https://github.com/eclipse/xtext/issues/1721</a>.</p>
+
+<h2 id="documentation">Documentation</h2>
+
+<p>The <a href="https://www.eclipse.org/Xtext/community.html">Xtext community website</a> and the <a href="https://www.eclipse.org/Xtext/documentation/index.html">Xtext documentation website</a> have been updated. New Xtext-based projects have been added, some editor features and the Unit testing / UI testing capabilities have been documented and the embedded code snippets have been updated as well.</p>
+
+<p>We further enhanced the <a href="https://github.com/eclipse/xtext/tree/master/dev-doc">Xtext Developer Documentation</a> to enable the community to easily contribute to Xtext.</p>
+
+<h2 id="code-generation-improvements">Code Generation improvements</h2>
+<p>This release contains some fixes to improve the generated code in the <code>src-gen</code> folders. The following files are affected:</p>
+
+<ul>
+ <li><code>Internal<dslName>.g</code> file in the <strong>runtime</strong> module - <a href="https://github.com/eclipse/xtext-core/issues/1467">xtext-core#1467</a></li>
+ <li><code>Internal<dslName>Parser.java</code> file in the <strong>runtime</strong> module - <a href="https://github.com/eclipse/xtext-core/issues/1467">xtext-core#1467</a></li>
+ <li><code><dslName>GrammarAccess.java</code> file in the <strong>runtime</strong> module - <a href="https://github.com/eclipse/xtext-core/issues/269">xtext-core#269</a></li>
+ <li><code>Partial<dslName>ContentAssistParser.java</code> file in the <strong>ide</strong> module - <a href="https://github.com/eclipse/xtext-core/issues/1418">xtext-core#1418</a></li>
+</ul>
+
+<p>We encourage you to regenerate your languages with the latest Xtext version. Usually you do not recognize any changes, unless you check-in the <code>src-gen</code> folders in a version control system.</p>
+
+<h2 id="eclipse-integration">Eclipse Integration</h2>
+
+<h2 id="upgrades">Upgrades</h2>
+
+<ul>
+ <li>Xtext 2.22 requires ASM 8.0.1 (updated from 7.2.0).</li>
+ <li>Maven Tycho was updated to version 1.7.0.</li>
+ <li>MWE(2) was updated to 2.11.3/1.5.3.</li>
+</ul>
+
+<h2 id="removals">Removals</h2>
+
+<ul>
+ <li>Xtext no longer has a direct dependency to ICU4J. If you use ICU4J in your codebase you should also consider to get rid of this dependencies as it will no longer be supported by Eclipse (Platform).</li>
+ <li>As announced in the 2.21 Release the deprecated API in the LSP area was removed.</li>
+ <li>We also removed the outdated leftovers of IDEA Support in <code>org.eclipse.xtext.xtext.generator</code>.</li>
+</ul>
+
+<h2 id="deprecations">Deprecations</h2>
+
+<ul>
+ <li><code>IXtext2EcorePostProcessor</code> & <code>XtendXtext2EcorePostProcessor</code> & <code>ProjectAwareXtendXtext2EcorePostProcessor</code> were deprecated as they depend on old Xpand/Xtend(1). As already announced in the <a href="2020-03-03-version-2-21-0.md">2.21 release notes</a> you should avoid depending on the old Xpand based <code>org.eclipse.xtext.generator</code> as well as on Xtend(1) based postprocessing. So if you have an <code>.ext</code> file right next to your <code>.xtext</code> file or subclass the interface it’s about time to switch to a manually maintained Ecore model.</li>
+</ul>
+
+<h2 id="credits">Credits</h2>
+
+<p>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 <a href="https://github.com/eclipse/xtext#repositories">all repositories</a> except <a href="https://github.com/eclipse/xtext-xtend">xtext-xtend</a>):</p>
+
+<ul>
+ <li>Christian Dietrich (itemis)</li>
+ <li>Tamas Miklossy (itemis)</li>
+ <li>Nico Prediger (itemis)</li>
+ <li>Sebastian Zarnekow (independent)</li>
+ <li>Karsten Thoms (Karakun)</li>
+ <li>Neeraj Bhusare (Zafin)</li>
+ <li>Arne Deutsch (itemis)</li>
+ <li>Jan Koehnlein (TypeFox)</li>
+ <li>George Suaridze (1C LLC) <img src="https://img.shields.io/badge/-first%20time%20contributor-green.svg" alt="" /></li>
+ <li>Mathias Rieder (Bachmann)</li>
+ <li>Mikael Barbero (Eclipse Foundation)</li>
+ <li>Titouan Vervack (Sigasi)</li>
+</ul>
+
+<h2 id="fixed-issues">Fixed Issues</h2>
+
+<p>As in every release cycle we were eagerly hunting down bugs, and reviewed and integrated plenty of contributions. For further details please refer to the following lists:</p>
+
+<ul>
+ <li>
+ <p><a href="https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+milestone%3ARelease_2.22+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&type=Issues&ref=searchresults">Fixed GitHub issues</a></p>
+ </li>
+ <li>
+ <p><a href="https://github.com/search?utf8=%E2%9C%93&q=is%3Apr+milestone%3ARelease_2.22+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&type=Issues&ref=searchresults">Closed Pull Requests</a></p>
+ </li>
+ <li>
+ <p><a href="https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&classification=Modeling&classification=Tools&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ckeywords&f0=OP&f1=OP&f3=CP&f4=CP&known_name=Xtext%202.22&list_id=16618269&product=TMF&product=Xtend&query_based_on=Xtext%202.22&query_format=advanced&status_whiteboard=v2.22&status_whiteboard_type=allwordssubstr">Fixed Eclipse Bugzilla tickets</a></p>
+ </li>
+</ul>
+
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+</div>
+
+ <footer class="site-footer">
+ <div id="extra">
+ <div class="inner">
+ <div class="container">
+ <div class="row">
+ <div class="span6">
+ <h3 class="footer-links-header">Quick Links</h3>
+ <ul class="footer-links clearfix">
+ <li><a href="http://www.eclipse.org/legal/privacy.php">Privacy Policy</a></li>
+ <li><a href="http://www.eclipse.org/legal/termsofuse.php">Terms of Use</a></li>
+ <li><a href="http://www.eclipse.org/legal/copyright.php">Copyright Agent</a></li>
+ <li><a href="http://www.eclipse.org/legal/">Legal</a></li>
+ </ul>
+ <ul class="footer-links clearfix">
+ <li><a href="http://www.eclipse.org">Eclipse Home</a></li>
+ <li><a href="http://marketplace.eclipse.org/">Market Place</a></li>
+ <li><a href="http://live.eclipse.org/">Eclipse Live</a></li>
+ <li><a href="http://www.planeteclipse.org/">Eclipse Planet</a></li>
+ </ul>
+ </div>
+ <div class="span6">
+ <!-- Social Media Links -->
+ <h3 class="footer-links-header"">Social Media</h3>
+ <ul class="footer-links clearfix">
+ <li>
+ <a href="https://twitter.com/xtext"><img src="/Xtext/images/Twitter-bird-darkgray.png" class="img-responsive" style="margin-right: 5px;height: 1em;" alt="Twitter icon">@xtext on Twitter</a>
+ </li>
+ </ul>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <a href="#" class="scrollup fadeOutRight animated" style="display: none;">ScrollUp</a>
+ <!-- Le javascript
+ ================================================== -->
+ <!-- Placed at the end of the document so the pages load faster -->
+
+ <script src="/Xtext/js/jquery-1.11.3.min.js"></script>
+ <script src="/Xtext/js/bootstrap.min.js"></script>
+ <script src="/Xtext/js/jquery.easing.1.3.js" type="text/javascript"></script>
+ <script src="/Xtext/js/jquery.prettyPhoto.js" type="text/javascript"></script>
+ <script src="/Xtext/js/prettify.js" type="text/javascript"></script>
+ <script src="/Xtext/js/lang-xtend.js" type="text/javascript"></script>
+ <script src="/Xtext/js/lang-common.js" type="text/javascript"></script>
+ <script src="/Xtext/js/custom.js" type="text/javascript"></script>
+ <!--script src="https://apis.google.com/js/platform.js" async defer></script-->
+ <!--script type="text/javascript">
+ var _gaq = _gaq || [];
+ _gaq.push([ '_setAccount', 'UA-2429174-3' ]);
+ _gaq.push([ '_trackPageview' ]);
+ (function() {
+ var ga = document.createElement('script');
+ ga.type = 'text/javascript';
+ ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? 'https://ssl'
+ : 'http://www')
+ + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0];
+ s.parentNode.insertBefore(ga, s);
+ })();
+ </script-->
+ <script src="/Xtext/js/coverflow.min.js" type="text/javascript"></script>
+ <script>
+ $(function() {
+ $('#coverflow').coverflow({
+ active : 1,
+ visibleAside: 2,
+ overlap : 0.5,
+ scale : 0.9,
+ angle : 20,
+ trigger : {
+ "itemfocus" : true,
+ "swipe" : true,
+ "mousewheel" : false
+ }
+ });
+ $('#coverflow :hidden').toggle();
+ $(window).resize(function() {
+ $('#coverflow').coverflow();
+ });
+ });
+
+ </script>
+</footer>
+
+
+ </body>
+
+</html>
