Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
31 commits
Select commit Hold shift + click to select a range
eaf1eb2
documentation: Document IDerivedStateComputer
tfonda-fbk Aug 2, 2024
6efbbfe
Merge pull request #75 from eclipse-xtext/published
cdietrich Nov 30, 2024
f43289a
prepare 2.38 website and rel notes
cdietrich Dec 4, 2024
793d139
Merge pull request #77 from eclipse-xtext/cd-prep-238
cdietrich Dec 5, 2024
63c136b
Merge pull request #78 from eclipse-xtext/published
cdietrich Dec 7, 2024
4811883
Merge pull request #80 from eclipse-xtext/published
cdietrich Dec 13, 2024
3ea2e08
Java 17 as the minimal Java version
LorenzoBettini Dec 16, 2024
54a1c6a
Document the new TemporaryFolder
LorenzoBettini Dec 16, 2024
94ab5b4
Also Xtend
LorenzoBettini Dec 16, 2024
243fb2c
Merge pull request #81 from eclipse-xtext/LorenzoBettini-patch-1
LorenzoBettini Dec 16, 2024
5de5732
document min emf version
cdietrich Dec 17, 2024
2e98099
Update 2025-03-04-version-2-38-0.md
LorenzoBettini Jan 2, 2025
4a1fd63
Merge pull request #83 from eclipse-xtext/LorenzoBettini-patch-2
LorenzoBettini Jan 2, 2025
1f9fc1a
Merge pull request #55 from tfonda-fbk/main
LorenzoBettini Jan 22, 2025
f056ca3
Fix links to the EMF project home page
tfonda-fbk Jan 23, 2025
7111bcc
Match link strings with actual URLs
tfonda-fbk Jan 23, 2025
5eda5bc
Merge pull request #84 from tfonda-fbk/links_fixes
LorenzoBettini Jan 23, 2025
668cbac
Document changes in IResourceSetupUtil
LorenzoBettini Jan 31, 2025
040d388
Merge pull request #85 from eclipse-xtext/LorenzoBettini-patch-2
LorenzoBettini Jan 31, 2025
228373a
Fix mismatched braces in the Outline styling example
tfonda-fbk Jan 23, 2025
c12cc68
Merge pull request #86 from tfonda-fbk/styling_example_fix
LorenzoBettini Feb 5, 2025
f7ab1db
Refer to GitHub in a uniform way
tfonda-fbk Feb 5, 2025
a1c21fb
Replace the Forum with GitHub Discussions in the Community page
tfonda-fbk Feb 5, 2025
13e3d54
Merge pull request #87 from tfonda-fbk/community_page_updates
LorenzoBettini Feb 5, 2025
7fa6404
Follow Xtext best practices in the Serialization documentation
tfonda-fbk Feb 17, 2025
0fdd1ba
Merge pull request #88 from tfonda-fbk/main
LorenzoBettini Feb 17, 2025
8e95186
document deprecation of TargetPlatformUtil
LorenzoBettini Feb 17, 2025
d3444a8
Merge pull request #89 from eclipse-xtext/LorenzoBettini-patch-2
LorenzoBettini Feb 17, 2025
4809d5f
Fix links in the 2.38 release notes
tfonda-fbk Feb 17, 2025
1ff436b
Merge pull request #90 from tfonda-fbk/links_fixes
LorenzoBettini Feb 17, 2025
e347a50
release 2.38.0
LorenzoBettini Feb 26, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# Eclipse Xtext Website

This repository contains the websites [xtext.org](https://eclipse.dev/Xtext) and [xtend-lang.org](https://eclipse.dev/Xtext/xtend). For general information about Xtext, see the [main repository](https://github.com/eclipse/xtext).
This repository contains the websites [https://eclipse.dev/Xtext/](https://eclipse.dev/Xtext) and [https://eclipse.dev/Xtext/xtend](https://eclipse.dev/Xtext/xtend). For general information about Xtext, see the [main repository](https://github.com/eclipse/xtext).

The [published](https://github.com/eclipse/xtext-website/tree/published) branch corresponds to what is published on the actual websites. Fixes that should be made visible immediately must be committed there. The [main](https://github.com/eclipse/xtext-website/tree/main) branch is used to write documentation and release notes for the next major or minor release of Xtext.
29 changes: 29 additions & 0 deletions xtend-website/_posts/releasenotes/2025-02-26-version-2-38-0.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
---
layout: post
title: Xtend 2.38.0 Release Notes
date: 2025-02-26
categories: releasenotes
published: true
---

## Call to Action: Secure the future maintenance of Xtext & Xtend

As you might have recognized, the number of people contributing to Xtext & Xtend 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 & especially Xtend 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/xtext/issues/1721](https://github.com/eclipse-xtext/xtext/issues/1721).

## Relevant changes

Xtend now requires Java 17 as the minimal Java version and 2024-03 as the minimal target platform.

## Credits

See Xtext release notes.

## 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:

* [Fixed GitHub issues](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+milestone%3ARelease_2.38+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](https://github.com/search?utf8=%E2%9C%93&q=is%3Apr+milestone%3ARelease_2.38+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 Eclipse Bugzilla tickets](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.30&list_id=16618269&product=TMF&product=Xtend&query_based_on=Xtext%202.30&query_format=advanced&status_whiteboard=v2.38&status_whiteboard_type=allwordssubstr)
4 changes: 2 additions & 2 deletions xtend-website/documentation/204_activeannotations.md
Original file line number Diff line number Diff line change
Expand Up @@ -240,13 +240,13 @@ Therefore, careful testing and debugging of the processor is essential. It is be
<dependency>
<groupId>org.eclipse.xtend</groupId>
<artifactId>org.eclipse.xtend.core</artifactId>
<version>2.37.0</version>
<version>2.38.0</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.eclipse.xtext</groupId>
<artifactId>org.eclipse.xtext.xbase.testing</artifactId>
<version>2.37.0</version>
<version>2.38.0</version>
<scope>test</scope>
</dependency>
```
Expand Down
6 changes: 3 additions & 3 deletions xtend-website/download.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ If you already have a project, you need to add the Xtend library:
<dependency>
<groupId>org.eclipse.xtend</groupId>
<artifactId>org.eclipse.xtend.lib</artifactId>
<version>2.37.0</version>
<version>2.38.0</version>
</dependency>
```

Expand All @@ -62,7 +62,7 @@ and the Xtend compiler plugin:
<plugin>
<groupId>org.eclipse.xtend</groupId>
<artifactId>xtend-maven-plugin</artifactId>
<version>2.37.0</version>
<version>2.38.0</version>
<executions>
<execution>
<goals>
Expand Down Expand Up @@ -90,7 +90,7 @@ plugins {
repositories.mavenCentral()

dependencies {
compile 'org.eclipse.xtend:org.eclipse.xtend.lib:2.37.0'
compile 'org.eclipse.xtend:org.eclipse.xtend.lib:2.38.0'
}
```

Expand Down
66 changes: 66 additions & 0 deletions xtext-website/_posts/releasenotes/2025-02-26-version-2-38-0.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
---
layout: post
title: Xtext 2.38.0 Release Notes
date: 2025-02-26
categories: releasenotes
published: true
---

## 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/xtext/issues/1721](https://github.com/eclipse-xtext/xtext/issues/1721).

## Relevant changes

* A new class, `TemporaryFolder,` has been added to the bundle `org.eclipse.xtext.testing`, meant to replace the class `TemporaryFolder`, now deprecated, in `org.eclipse.xtext.xbase.testing`. Clients should update to the new class: the deprecated one will be removed in the future.
* Our project wizard for Maven/Tycho projects now generates this dependency for the `exec-maven-plugin` configuration for running the MWE2 workflow:

```xml
<dependency>
<groupId>org.eclipse.xtext</groupId>
<artifactId>org.eclipse.xtext.xtext.generator.dependencies</artifactId>
<version>${xtextVersion}</version>
</dependency>
```

to avoid possible problems with EMF/Platform dependencies (e.g., `NoSuchMethodError`) due to misaligned transitive dependencies.
This replaces the previously generated dependency `xtext-antlr-generator`, which is included in the new dependency.
For existing projects, we suggest to perform such a change manually.
The `org.eclipse.xtext.xtext.generator.dependencies` bundle was introduced in the previous release.
* A new method was introduced, `IResourcesSetupUtil.waitForJdtIndex`, that blocks until the JDT index finishes its indexing. This is now automatically called from `waitForBuild`, `cleanBuild` and `fullBuild`. This new mechanism removed flaky UI tests from our builds.

## Breaking changes

Xtext now requires Java 17 as the minimal Java version and 2024-03 as the minimal target platform.

## Upgrades

## Deprecations

- The method `IResourcesSetupUtil.isAutobuild(boolean)` has been deprecated and will be removed in a future release; its parameter was never used. The new method `IResourcesSetupUtil.isAutobuild()` should be used instead.
- The class `TargetPlatformUtil` and its method `setTargetPlatform` have been deprecated: with recent versions of Tycho and PDE, they are not needed anymore.

## 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
- Mehmet Emin Karaman
- Rubén Porras Campo
- Martin Jobst
- Tommaso Fonda
- Ed Merks

## 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:

* [Fixed GitHub issues](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+milestone%3ARelease_2.38+is%3Aclosed+repo%3Aeclipse-xtext%2Fxtext&type=issues&ref=searchresults)

* [Closed Pull Requests](https://github.com/search?utf8=%E2%9C%93&q=is%3Apr+milestone%3ARelease_2.38+is%3Aclosed+repo%3Aeclipse-xtext%2Fxtext&type=pullrequests&ref=searchresults)

* [Fixed Eclipse Bugzilla tickets](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.38&list_id=16618269&product=TMF&product=Xtend&query_based_on=Xtext%202.38&query_format=advanced&status_whiteboard=v2.38&status_whiteboard_type=allwordssubstr)
28 changes: 23 additions & 5 deletions xtext-website/community.html
Original file line number Diff line number Diff line change
Expand Up @@ -9,16 +9,16 @@ <h2>Resources</h2>
<div class="row">
<div class="span1">&nbsp;</div>
<div class="span9 team">
<a href="https://www.eclipse.org/forums/index.php?t=thread&frm_id=27" class="anchor-in-div"></a>
<a href="https://github.com/eclipse-xtext/xtext/discussions" class="anchor-in-div"></a>
<div class="row">
<div class="span1 ">
<img src="{{ site.baseurl }}/images/discussion-circ-darkgray.png" alt="image" class="image_left">
</div>
<div class="span2 ">
<h3>Forum</h3>
<h3>GitHub Discussions</h3>
</div>
<div class="span6 ">
<p>The <strong>Xtext&#x2122; forum</strong> is the first source for getting answers in case you got stuck.
<p><strong>Xtext&#x2122; GitHub Discussions</strong> is the first source for getting answers in case you got stuck.
The community is very friendly.</p>
</div>
</div>
Expand All @@ -37,7 +37,7 @@ <h3>Forum</h3>
<h3>Found a Bug?</h3>
</div>
<div class="span6 ">
<p>Bug reports and enhancement request are tracked at <strong>GitHub.org</strong>. Please
<p>Bug reports and enhancement request are tracked at <strong>GitHub.com</strong>. Please
explain the problem and provide a reduced but reproducible example.</p>
</div>
</div>
Expand All @@ -53,7 +53,7 @@ <h3>Found a Bug?</h3>
<img src="{{ site.baseurl }}/images/github-mark-darkgray.png" alt="image" class="image_left">
</div>
<div class="span2 ">
<h3>Github</h3>
<h3>GitHub</h3>
</div>
<div class="span6 ">
<p>The Xtext&#x2122; source code is available on <strong>GitHub</strong>. You'll find more information on how to contribute to the project in the README.md contained there.</p>
Expand All @@ -80,6 +80,24 @@ <h3>Twitter</h3>
</div>
<div class="span1">&nbsp;</div>
</div>
<div class="row">
<div class="span1">&nbsp;</div>
<div class="span9 team">
<a href="https://www.eclipse.org/forums/index.php?t=thread&frm_id=27" class="anchor-in-div"></a>
<div class="row">
<div class="span1 ">
<img src="{{ site.baseurl }}/images/discussion-circ-darkgray.png" alt="image" class="image_left">
</div>
<div class="span2 ">
<h3>Forum (archived)</h3>
</div>
<div class="span6 ">
<p>The <strong>Xtext&#x2122; forum</strong>, now read-only, is still a useful resource, as it contains several years' worth of discussion about Xtext.</p>
</div>
</div>
</div>
<div class="span1">&nbsp;</div>
</div>
</div>
<br/><br/>
<div id="zoo" class="container">
Expand Down
4 changes: 2 additions & 2 deletions xtext-website/documentation/301_grammarlanguage.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ The second aspect that can be deduced from the first line of the grammar is its

### EPackage Declarations {#package-declarations}

Xtext parsers create in-memory object graphs while consuming text. Such object-graphs are instances of [EMF](https://www.eclipse.org/modeling/emf/) Ecore models. An Ecore model basically consists of an EPackage containing EClasses, EDataTypes and EEnums (see the [section on EMF](308_emf_integration.html#model-metamodel) for more details) and describes the structure of the instantiated objects. Xtext can infer Ecore models from a grammar (see [Ecore model inference](301_grammarlanguage.html#metamodel-inference)) but it is also possible to import existing Ecore models. You can even mix both approaches and use multiple existing Ecore models and infer some others from a single grammar. This allows for easy reuse of existing abstractions while still having the advantage of short turnarounds with derived Ecore models.
Xtext parsers create in-memory object graphs while consuming text. Such object-graphs are instances of [EMF](https://projects.eclipse.org/projects/modeling.emf.emf) Ecore models. An Ecore model basically consists of an EPackage containing EClasses, EDataTypes and EEnums (see the [section on EMF](308_emf_integration.html#model-metamodel) for more details) and describes the structure of the instantiated objects. Xtext can infer Ecore models from a grammar (see [Ecore model inference](301_grammarlanguage.html#metamodel-inference)) but it is also possible to import existing Ecore models. You can even mix both approaches and use multiple existing Ecore models and infer some others from a single grammar. This allows for easy reuse of existing abstractions while still having the advantage of short turnarounds with derived Ecore models.

#### EPackage Generation

Expand Down Expand Up @@ -766,4 +766,4 @@ terminal ANY_OTHER:

---

**[Next Chapter: Configuration](302_configuration.html)**
**[Next Chapter: Configuration](302_configuration.html)**
Loading