Table of Contents

Xtext 2.35.0 Release Notes  May 28, 2024


Xtext 2.35.0 …

Call to Action: Secure the future maintenance of Xtext

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, at least in the current form and as part of the Eclipse Simrel. If you care, please join the discussion in https://github.com/eclipse/xtext/issues/1721.

Relevant changes

Initial support for Java 21

IMPORTANT: before switching to Java 21, make sure to go through the deprecation notice below about org.eclipse.xtext.xbase.lib.IterableExtensions.last(Iterable<T>).

In Eclipse, using a recent JDT version, Xbase languages, including Xtend, can access Java 21 generated byte-code and refer to Java records.

For Maven/Tycho builds, e.g., xtext-maven-plugin and xtend-maven-plugin, a new version of jdt.core, e.g., 3.37.0, must be forced (currently, in the BOM, we still use an older version of JDT).
This can be achieved by passing the system property -Djava-21 when running Maven (our BOM will automatically activate the new version of JDT).
Alternatively, you can place the line -Djava-21 in your .mvn/maven.config file in the root folder.

For Gradle, you need to force the dependency of the new version of jdt.core, e.g., 3.37.0.

Normalization of EOLs in Xbase multi-line strings

In Xbase languages (including Xtend), multi-line strings (that is, strings that span several lines, NOT Xtend template expressions) are now normalized concerning end-of-line characters, following the same strategies of Normalization Of Line Terminators in Java Text Blocks: Windows CR in the DSL textual sources will not be part of the string in the generated Java code, which will only contain Unix LF.
This change leads to the same Java code generated in Windows and Unix-like systems (see issue https://github.com/eclipse/xtext/issues/2293).

This DSL string

var s = "a multi
line string"

Will always result in the following generated Java code in Windows, Linux, and macOS:

String s = "a multi\nline string";

While before, in Windows, it would have been:

String s = "a multi\r\nline string";

Note that the behavior for explicit escape sequences (\\r) will remain the same as before.

Automatic validation for Xbase languages

The new JvmGenericTypeValidator was introduced to automatically perform several Java-related checks in the hierarchy of the inferred JvmGenericTypes of an Xbase language, with the corresponding error reporting.
For example, cycles in a hierarchy, extension of a final class, proper extension of an abstract class (do you implement all the abstract methods or declare the inferred class as abstract?), proper method overriding, etc. It also performs duplicate elements checks, like duplicate parameter names, duplicate fields and duplicate methods (keeping the type-erasure into consideration when using types with arguments).

This mechanism assumes that you implement the JvmModelInferrer “correctly”.
It only checks the first inferred JvmGenericType for the same DSL element (i.e., if for an element Entity you infer two JvmGenericTypes, t1 and t2, only the first one will be checked).
Moreover, it only checks Jvm model elements with an associated source element.
Concerning intended classes to extend and interfaces to extend/implement, it assumes the model inferrer uses the new JvmTypesBuilder#setSuperClass(JvmDeclaredType, JvmTypeReference) and JvmTypesBuilder#addSuperInterface(JvmDeclaredType, JvmTypeReference), respectively.

Currently, this validator must be enabled explicitly through the composedCheck in the MWE2 file or the @ComposedChecks annotation in the validator, e.g., @ComposedChecks(validators = JvmGenericTypeValidator.class).

The Domainmodel example now uses this validator.
The Xtend validator has been refactored to also use this validator.

Maven building

When using xtext-maven-plugin for Xbase languages, relative paths (instead of absolute paths) are now generated in the ._trace files.

The configuration option writeStorageResources has been added to xtext-maven-plugin to write the semantic model, the resource description, and optionally the node model to a ResourceStorage (.bin files).
See this integration test for an example.

To single-source the configuration of a language that is built with Maven, the configuration options writeClasspathConfiguration and classpathConfigurationLocation were added to the xtext-maven-plugin. If enabled, a property file will be written that contains the classpath information, model directories, output directories and lookup paths that were used for the plugin execution. The properties file contains file hashes that allow to track changed across subsequent runs.

Initial LSP Support for Xbase Languages

The initial support for language servers that use Xbase languages is part of this release. It’s based on binary Java resources and uses the classpath configuration that’s written by the maven plugin. Thereby, the Xtext language server can be configured such that Xbase language can resolve against class files from the current project. If a Java language server runs in parallel to the Xtext language server, and incrementally produces class files, the changes will be picked up by the Xtext language server.

Node model customizing

Low level APIs were added that allow to customizing the node model and the way it is stored on the EMF objects. This enables advanced use cases like unloading the node model for resources that are already fully resolved. The node model can be re-attached on demand for these cases. Curious users may want to configure the DetachableNodeModelFragment in their mwe2 workflows.

Initial Support for TextMate Grammars

The highly configurable DetachableNodeModelFragment can be configured in the mwe2 workflow to emit textmate grammar to drive the lexical coloring in LSP clients that do have support for tm-language definitions.

Runtime Testing

The AbstractFormatterTest base class has been added to the org.eclipse.xtext.testing package to provide a convenient way to test the formatter capabilities. The Xtext Domainmodel example project and the Xtend code base have been extended by concrete formatter test cases to demonstrate the usage of this framework class.

The generated InjectorProvider for runtime tests has been improved to make customizations easier w.r.t. OSGI/Maven environments (see https://github.com/eclipse/xtext/pull/3042).

The base class AbstractXtextTests, for “old”-style testing, is now part of org.eclipse.xtext.testing. (See also the removal notice below.)

Two new methods were added org.eclipse.xtext.xbase.testing.CompilationTestHelper.Result.assertNoErrors()/assertNoIssues() for checking whether during the compilation of the input sources errors, respectively, errors or warnings, were detected.

UI Testing

The AbstractContentAssistTest class has been extended by API methods to provide a convenient way to test proposals from several resources. The StatemachineContentAssistTest test class of the Xtext Statemachine example project demonstrates the usage of these new API methods.

Upgrades

  • GSON is now on 2.11
  • Guava was update to 33.2
  • lsp4j is now on 0.23.x
  • MWE(2) is now on 1.12/2.18

Deprecations

The method org.eclipse.xtext.xbase.lib.IterableExtensions.last(Iterable<T>) has been deprecated in favor of the new org.eclipse.xtext.xbase.lib.IterableExtensions.lastOrNull(Iterable<T>).
The reason is that Java 21 introduces the getLast method in a few collection classes.
Xbase will prefer getLast to our extension method last to generate Java code when the runtime is Java 21 and the last extension method is used in an Xbase DSL code, e.g., Xtend.
The problem is that our extension method last returns null when the collection is empty, while the getLast method in Java 21 throws a NoSuchElementException, leading to different semantics.

We encourage everyone to pay attention to such deprecations and switch to the new lastOrNull, which retains the semantics of last, before switching to Java 21.
To keep the consistency between IterableExtensions and IteratorExtensions we also deprecated last in the latter and introduced lastOrNull in IteratorExtensions.

Future removals notice

In the next release, 2.36.0, the long time deprecated org.eclipse.xtext.junit4 and org.eclipse.xtext.xbase.junit will be removed.
The projects org.eclipse.xtext.testing, org.eclipse.xtext.ui.testing, org.eclipse.xtext.xbase.testing and org.eclipse.xtext.xbase.ui.testing already provide replacements for the above deprecated projects.
Note that the old base class AbstractXtextTests is now part of org.eclipse.xtext.testing.

Credits

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).

  • Lorenzo Bettini
  • Christian Dietrich
  • Sebastian Zarnekow
  • Hannes Wellmann
  • Tamas Miklossy
  • Ed Merks
  • Rubén Porras Campo
  • Didier Vojtisek
  • Ehab Younes
  • Florian Pirchner

Fixed Issues

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:

Xtext 2.34.0 Release Notes  Feb 27, 2024


Xtext 2.34.0 is a maintenance release.

Call to Action: Secure the future maintenance of Xtext

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, at least in the current form and as part of the Eclipse Simrel. If you care, please join the discussion in https://github.com/eclipse/xtext/issues/1721.

Upgrades

  • Guava was update to 33.0.0
  • MWE(2) is now on 1.11/2.17

Removals

Credits

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).

  • Lorenzo Bettini
  • Christian Dietrich
  • Sebastian Zarnekow
  • Stephan Herrmann
  • Jonathan Pollert
  • annes Wellmann

Fixed Issues

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:

Xtext 2.33.0 Release Notes  Nov 21, 2023


Xtext 2.33.0 is a maintenance release.

Call to Action: Secure the future maintenance of Xtext

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, at least in the current form and as part of the Eclipse Simrel. If you care, please join the discussion in https://github.com/eclipse/xtext/issues/1721.

Upgrades

  • Guava was update to 32.1.3
  • Reload4j was updated to 1.2.25
  • Classgraph was updated to 4.8.164. The bundle id in orbit has changed so you may need to adapt.
  • ASM is now on 9.6
  • MWE(2) is now on 1.10/2.16

Removals

  • Old Xpand based org.eclipse.xtext.generator and IXtext2EcorePostProcessor have been removed.

Credits

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).

  • Christian Dietrich
  • Sebastian Zarnekow
  • Hannes Wellmann
  • Heinrich Weichert
  • Wouter Born

Fixed Issues

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:

Xtext 2.32.0 Release Notes  Aug 27, 2023


Xtext 2.32.0 is a maintenance release.

Call to Action: Secure the future maintenance of Xtext

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, at least in the current form and as part of the Eclipse Simrel. If you care, please join the discussion in https://github.com/eclipse/xtext/issues/1721.

Upgrades

  • Guava was update to 32.1.2
  • Guice is now on 7.0.0 javax.inject annotations are no longer suported. Use the ones from guice or jakarta.inject.
  • MWE was updated to 2.15.0
  • Gradle is on 8.2
  • xtext-web now uses jakarta.servlet api

For removal reminder

  • Please remember the old xpand based org.eclipse.xtext.generator as well as the Xpand/Xtend(1) based metamodel postprocessor are deprecated and marked for removal.

Credits

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.

  • Christian Dietrich
  • Shashwat Anand (Advantest)
  • Ruben Porras (Avaloq)
  • Florian Pirchner
  • Jan Rosczak (Hapag-Lloyd)
  • Joao Ferreira (Avaloq)
  • Lorenzo Bettini (Università degli Studi di Firenze)
  • Sebastian Zarnekow

Fixed Issues

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:

Xtext 2.31.0 Release Notes  May 29, 2023


Xtext 2.31.0 is a maintenance release.

Call to Action: Secure the future maintenance of Xtext

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, at least in the current form and as part of the Eclipse Simrel. If you care, please join the discussion in https://github.com/eclipse/xtext/issues/1721.

Xtext Monorepo

Xtext is now built from the new Monorepo at https://github.com/eclipse/xtext and built with Maven only. Many thanks to Lorenzo Bettini for the great effort to make this possible.

Upgrades

  • LSP4J is now on 0.21.0
  • ASM is now on 5.9
  • Junit5 was updated to 5.9.3

Changes / Enhancements

  • Xtext hovers now support disposing browsers on timeout (see https://github.com/eclipse/xtext/issues/2653 and linked platform and jdt issues and pr there)
  • Our DebugSourceInstallingCompilationParticipant now makes use of JDTs feature to do the bytecode manipulation without extra reading and writing the file.

Credits

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.

  • Lorenzo Bettini (Università degli Studi di Firenze)
  • Christian Dietrich (itemis)
  • Hannes Wellmann (IILS mbH)
  • Christian Schneider (TypeFox)
  • Ed Merks
  • Sebastian Zarnekow (independent)

Fixed Issues

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:

Xtext 2.30.0 Release Notes  Feb 27, 2023


Xtext 2.30.0 is a maintenance release.

Call to Action: Secure the future maintenance of Xtext

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, at least in the current form and as part of the Eclipse Simrel. If you care, please join the discussion in https://github.com/eclipse/xtext/issues/1721.

Upgrades

  • EMF is now at 2.29 and later.
  • Jetty 9.4.50
  • We pinned the versions in manifests to match the ones in the minimal target platform for Eclipse 2022-03.
  • Reload4j/log4j is now at 1.2.24
  • LSP4J was updated to 0.20.0 and GSON to 2.10.1

Changes / Enhancements

The minimal version for Eclipse Platform and JDT in manifests were bumped so that they correspond to our minimal tested target platform of Eclipse 2022-03.
The performance of (overloaded) Xbase expressions was enhanced.

Deprecation

We marked Deprecated API more explicit and also added some forRemoval to them.

Credits

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 all repositories except xtext-xtend):

Christian Dietrich (itemis)
Lorenzo Bettini (Università degli Studi di Firenze)
Sebastian Zarnekow (independent)
Elie Richa (AdaCore)

Fixed Issues

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:

Xtext 2.29.0 Release Notes  Nov 21, 2022


Xtext 2.29.0 is a maintenance release.

Call to Action: Secure the future maintenance of Xtext

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, at least in the current form and as part of the Eclipse Simrel. If you care, please join the discussion in https://github.com/eclipse/xtext/issues/1721.

Xtext and Java 17

Xtext now supports Java 17 as source and target, too. This requires newer Eclipse platform and JDT versions that do no longer run on Java 8. That’s why the Xtext framework and Xtend compiler require Java 11 as minimal Java version from 2.29 onwards. While we were at it we also bumped the minimal tested Eclipse version to 2022-03 (2.28 was still compatible to and tested against Eclipse Oxygen). Please Note: We did no special treatment for newer Java constructs in Xtend, so what works, works, what does not, does not - the latter being most likely intentional. Please engage by filing bugs or pull requests (see also issue#1982.

Upgrades

  • LSP4J was updated to 0.19.0
  • GSON to 2.9.1
  • Classgraph is now at 4.8.149
  • ASM is now on 9.4
  • MWE(2) is now at 1.8.0 / 2.14.0
  • JUnit5 at 5.9.1

Changes / Enhancements

Standalone Builder

The Incremental Standlone Builder is now capable of performing incremental builds. Depending on the changes that happened since the previous compile run, only a subset of the model files need to be processed. Both model and Java file changes as well as class-path changes are taken into account. The feature is opt-in since it might break backwards compatibility for DSLs that use non-default code generation patterns. Incremental builds can also be enabled for the Xtext maven plugin xtext-extras#805.

<plugins>
    <plugin>
        <groupId>org.eclipse.xtext</groupId>
        <artifactId>xtext-maven-plugin</artifactId>
        <configuration>
            <languages>
                <language>
                    <javaSupport>(true|false)</javaSupport>
                    <setup>..MyDslStandaloneSetup</setup>
                </language>
            </languages>
            <incrementalXtextBuild>true</incrementalXtextBuild>
        </configuration>
        <dependencies>
            <dependency>
                ..
            </dependency>
        </dependencies>
    </plugin>
</plugins>

LSP

Language server now has a beta version of semantic token support.

Credits

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 all repositories except xtext-xtend):

  • Christian Dietrich (itemis)
  • Sebastian Zarnekow (independent)
  • Ruben Porras
  • Lorenzo Bettini (Università degli Studi di Firenze)

Fixed Issues

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:

Xtext 2.28.0 Release Notes  Aug 29, 2022


Xtext 2.28.0 is a maintenance release.

Call to Action: Secure the future maintenance of Xtext

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, at least in the current form and as part of the Eclipse Simrel. If you care, please join the discussion in https://github.com/eclipse/xtext/issues/1721.

Changes to org.eclipse.xtext.sdk feature.

The org.eclipse.xtext.sdk does no longer package the deprecated org.eclipse.xtext.generator bundle. Please migrate to the new workflow/generator. The old and deprecated generator can still be found in the new org.eclipse.xtext.generator feature.

Upgrades

  • LSP4J was updated to 0.15.0
  • GSON was updated to 2.9.0

Changes / Enhancements

  • LSP Code was optimized and enhanced. We have e.g. done some enhancements to Quickfix API.
  • Xtext Supports M2E 2.x
  • Xbase based formatters now can be subclassed in Java more easily.
  • Better support for needRebuild api in platform.

Credits

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 all repositories except xtext-xtend):

Christian Dietrich (itemis)
Ruben Porras
Karsten Thoms (karakun)
Frank Benoit (ETAS)
Hannes Wellmann (IILS mbH)

Fixed Issues

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:

Xtext 2.27.0 Release Notes  May 30, 2022


Xtext 2.27.0 is a maintenance release.

Call to Action: Secure the future maintenance of Xtext

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, at least in the current form and as part of the Eclipse Simrel. If you care, please join the discussion in https://github.com/eclipse/xtext/issues/1721.

Changes to org.eclipse.xtext.sdk feature.

The org.eclipse.xtext.sdk does no longer package the deprecated org.eclipse.xtext.generator bundle. Please migrate to the new workflow/generator. The old and deprecated generator can still be found in the new org.eclipse.xtext.generator feature.

Upgrades

  • Tycho 2.7.3
  • Xtext now uses Reload4j 1.2.19
  • Gradle 7.4.2 / xtext-gradle-plugin 3.0.2
  • ASM 9.3
  • MWE(2) to 1.7.0 / 2.13.0
  • LSP4j is now on version 0.14.0 / protocol version 3.17.0

Changes

  • The qualifiers of org.antlr.runtime,javax.xml,org.aopalliance have changed due to (breaking) changes in orbit.

Enhancements

  • Xtext makes now use of the enhanced possibilities for requesting rebuilds in platform. Please test this in your environments and give feedback
  • The experimental API for Quickfix code actions of the Xtext Language Server Protocol (LSP) implementation has been extended to support textual quickfixes. This comes in addition to the existing support for semantic quickfixes

Removals

  • Xtext no longer depends on commons lang

Credits

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 all repositories except xtext-xtend):

  • Christian Dietrich (itemis)
  • Lorenzo Bettini (Università degli Studi di Firenze)
  • Ruben Porras
  • Sebastian Zarnekow (independent)
  • Lukas Foerner
  • Titouan Vervack (Sigasi)

Fixed Issues

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:

Xtext 2.26.0 Release Notes  Feb 28, 2022


Xtext 2.26.0 is a maintenance release.

Call to Action: Secure the future maintenance of Xtext

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, at least in the current form and as part of the Eclipse Simrel. If you care, please join the discussion in https://github.com/eclipse/xtext/issues/1721.

Xtext and Java 17

Xtext now supports running on Java 17 with Java 8 and 11 targets. Source and Target 17 are not supported yet and are planned for Xtext 2.27.0. This will also require dropping Java 8 in the next release.

Upgrades

  • Tycho was updated to 2.6.0
  • GSON was updated to 2.8.9
  • LSP4J was updated to 0.12.0 / protocol version 3.16.0
  • Xtext now uses Guice 5.0.1 and thus the warnings on Java 11+ should be gone.
  • ASM was updated to 9.2
  • Gradle (in Wizard) is now updated to 7.x and the xtext-gradle-plugin to 3.0.1
  • Classgraph is updated to 4.8.137

Enhancements

  • The Xtext LSP implementation has learned folding support.
  • xtext-maven#139 : xtext-maven can now install trace information for DSLs with a derived Java model (for example languages using Xbase).
  • Dependencies to Log4j are now less restrictive so that you should be able to use reload4j as drop-in replacement.

Deprecations

  • The already deprecated MergeableManifest classes we marked “for removal”. Make sure you do not longer use them.
  • We will drop support for GWT in a future release.
  • The next Xtext version will likely no long support Java versions below Java 11.

Credits

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 all repositories except xtext-xtend):

Christian Dietrich (itemis)
Karsten Thoms (Karakun)
Sebastian Zarnekow (independent)
Ruben Porras
Dennis Hübner (TypeFox)
Stefan Oehme (independent)
Titouan Vervack (Sigasi)
Edmundo Lopez
Mark Sujew (TypeFox)
Michael Keppler (ETAS)
Tamas Miklossy (itemis)
Nico Prediger (itemis)
Heinrich Weichert (AVL DiTEST)
Lawrence Goossens (Sigasi)
Oliver Libutzki (independent)

Fixed Issues

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: