diff --git a/org.eclipse.xtend.doc/contents/204_activeannotations.html b/org.eclipse.xtend.doc/contents/204_activeannotations.html index 418bc5fc83d..eb749853d1e 100644 --- a/org.eclipse.xtend.doc/contents/204_activeannotations.html +++ b/org.eclipse.xtend.doc/contents/204_activeannotations.html @@ -238,13 +238,13 @@

Class Path Setup and Testing

<dependency>
   <groupId>org.eclipse.xtend</groupId>
   <artifactId>org.eclipse.xtend.core</artifactId>
-  <version>2.35.0</version>
+  <version>2.37.0</version>
   <scope>test</scope>
 </dependency>
 <dependency>
   <groupId>org.eclipse.xtext</groupId>
   <artifactId>org.eclipse.xtext.xbase.testing</artifactId>
-  <version>2.35.0</version>
+  <version>2.37.0</version>
   <scope>test</scope>
 </dependency>
diff --git a/org.eclipse.xtext.doc/contents/305_xbase.html b/org.eclipse.xtext.doc/contents/305_xbase.html index 58d5efd6409..467a008413d 100644 --- a/org.eclipse.xtext.doc/contents/305_xbase.html +++ b/org.eclipse.xtext.doc/contents/305_xbase.html @@ -224,12 +224,12 @@

Linking and Indexing

Validation

-

Besides your custom validations, you can use JvmGenericTypeValidator, introduced in version 2.35.0. This automatically perform several Java-related checks in the hierarchy of the inferred JvmGenericTypes of an Xbase language, with the corresponding error reporting. +

Besides your custom validations, you can use JvmGenericTypeValidator, introduced in version 2.35.0. This 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 IJvmModelInferrer “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. +

This mechanism assumes that you implement the IJvmModelInferrer “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 JvmTypesBuilder methods setSuperClass(JvmDeclaredType, JvmTypeReference) and 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).

diff --git a/org.eclipse.xtext.doc/contents/310_eclipse_support.html b/org.eclipse.xtext.doc/contents/310_eclipse_support.html index 34024124b0a..11124a4f764 100644 --- a/org.eclipse.xtext.doc/contents/310_eclipse_support.html +++ b/org.eclipse.xtext.doc/contents/310_eclipse_support.html @@ -551,9 +551,9 @@

Location Provider

The location service offers different methods to obtain the region of interest for special use cases. You can either obtain the complete region for an object or only the identifying string which is usually the name of the instance (see getSignificantTextRegion(EObject)). You can also query for the text region of a specific EStructuralFeature by means of getFullTextRegion(EObject, EStructuralFeature, int).

-

As the default strategy is a best effort it may not always result in the selection you want. If that’s the case you can override the ILocationInFileProvider binding in the UI module as in the following example:

+

As the default strategy is a best effort it may not always result in the selection you want. If that’s the case you can override the ILocationInFileProvider binding in the runtime module as in the following example:

-
public class MyDslUiModule extends AbstractMyDslUiModule {
+
public class MyDslRuntimeModule extends AbstractMyDslRuntimeModule {
   @Override
   public Class<? extends ILocationInFileProvider> 
       bindILocationInFileProvider() {
diff --git a/org.eclipse.xtext.doc/contents/340_lsp_support.html b/org.eclipse.xtext.doc/contents/340_lsp_support.html
index 0b926cae8d9..3ff5740f9a2 100644
--- a/org.eclipse.xtext.doc/contents/340_lsp_support.html
+++ b/org.eclipse.xtext.doc/contents/340_lsp_support.html
@@ -79,6 +79,8 @@ 
Getting Started in Eclipse

 "uuid": "8383e49a-fa0d-4bb5-827b-10e8abb294ca"
 }
 

+    
You may save the content in a file and then add it to the TextMate grammar in Preferences.

+Domainmodel Language Server Launcher

   
   
  • Open a *.dmodel file with the Generic Editor and explore the supported language features like syntax highlighting, content assist, validation, displaying code lenses, quickfixes, formatting, … :
    
 Domainmodel Language Features
    • 
diff --git a/org.eclipse.xtext.doc/contents/350_continuous_integration.html b/org.eclipse.xtext.doc/contents/350_continuous_integration.html
index 0d67246f98f..755ddd59331 100644
--- a/org.eclipse.xtext.doc/contents/350_continuous_integration.html
+++ b/org.eclipse.xtext.doc/contents/350_continuous_integration.html
@@ -313,6 +313,22 @@ 
    Maven Tycho Hints
    
     
   
   
+    
+      2.37.0
+      2.39.0 (2.29.0)
+      2.20.0 (2.9.1)
+      no longer supported
+      4.34.0 (4.24)
+      2024-12
+    
+    
+      2.36.0
+      2.38.0 (2.29.0)
+      2.19.0 (2.9.1)
+      no longer supported
+      4.33.0 (4.23)
+      2024-09
+    
     
       2.35.0
       2.38.0 (2.29.0)
@@ -556,7 +572,7 @@ 
    Maven Tycho Hints
    
   
 
 
-
    The following is an example target platform definition for Xtext 2.35.0 and Eclipse 4.32 alias 2024-06.
    
+
    The following is an example target platform definition for Xtext 2.37.0 and Eclipse 4.34 alias 2024-12.
    
 
 
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <?pde version="3.8"?>
@@ -564,7 +580,7 @@ 
    Maven Tycho Hints
    
 <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="https://download.eclipse.org/modeling/tmf/xtext/updates/releases/2.35.0/"/>
+    <repository location="https://download.eclipse.org/modeling/tmf/xtext/updates/releases/2.37.0/"/>
   </location>
   <location includeAllPlatforms="false" includeConfigurePhase="false" includeMode="planner" includeSource="false" type="InstallableUnit">
     <unit id="org.eclipse.jdt.feature.group" version="0.0.0"/>
@@ -573,7 +589,7 @@ 
    Maven Tycho Hints
    
     <unit id="org.eclipse.draw2d.feature.group" version="0.0.0"/>
     <unit id="org.eclipse.emf.sdk.feature.group" version="0.0.0"/>
     <unit id="org.eclipse.emf.mwe2.launcher.feature.group" version="0.0.0"/>
-    <repository location="https://download.eclipse.org/releases/2024-06/"/>
+    <repository location="https://download.eclipse.org/releases/2024-12/"/>
   </location>
 </locations>
 </target>