Maven import fails with Nisse + Maven Tiles on VS Code Java 1.46.0 (works on 1.45.0)
Maintainer antworten meist innerhalb von 1 Tag
@snjeza arbeitet bereits daran.
Seit 03.11.2025.
Bewertung
Dieses Issue wurde noch nicht bewertet.
Beschreibung
Bug: Maven import fails with Nisse + Maven Tiles on VS Code Java 1.46.0 (works on 1.45.0)
Summary
When opening a Maven project that uses both Nisse dynamic versioning (Maven Core Extension) and Maven Tiles, the Red Hat Java language server fails to import the project on VS Code Java extension 1.46.0 (JDT LS 1.51.0).
- ✅ Using only Nisse works fine.
- ✅ Using only Maven Tiles works fine.
- ❌ The issue occurs only when Nisse and Maven Tiles are used together.
This appears to be a regression in how JDT LS handles Maven model building when multiple Maven extensions (provided via maven.ext.class.path) interact during the import phase.
Reproduction Steps
-
Clone the two minimal reproduction repositories:
- Tile project: https://github.com/lfvJonas/vscode-issue-example-tile
- Main project: https://github.com/lfvJonas/vscode-issue-example-project
-
Install the tile locally:
mvn clean install -
Generate the required Nisse Maven extension classpath to MAVEN_OPTS:
mvn eu.maveniverse.maven.plugins:toolbox:0.14.0:gav-classpath -Dgav=eu.maveniverse.maven.nisse:extension3:0.6.1The output will look something like this:
[INFO] /home/<user>/.m2/repository/eu/maveniverse/maven/nisse/extension3/0.6.1/extension3-0.6.1.jar:/home/<user>/.m2/repository/eu/maveniverse/maven/nisse/core/0.6.1/core-0.6.1.jar:... -
Set the
MAVEN_OPTSenvironment variable using that output:export MAVEN_OPTS="-Dnisse.source.jgit.dynamicVersion=true -Dmaven.ext.class.path=${output form previous command}" -
Verify that the project builds successfully on the command line:
mvn clean install -
Open
vscode-issue-example-projectin VS Code with the Red Hat Java extension 1.46.0, and wait for import.
Expected Behavior
The project should import successfully (as it does with version 1.45.0).
Actual Behavior (only on 1.46.0)
Project import fails during Maven model building with:
org.apache.maven.model.building.ModelBuildingException: ... effective model for com.example:demo:${nisse.jgit.dynamicVersion}
[WARNING] 'version' contains an expression but should be a constant. @ line 9, column 11
[ERROR] 'version' must be a constant version but is '${nisse.jgit.dynamicVersion}'. @ line 9, column 11
at io.repaint.maven.tiles.TilesMavenLifecycleParticipant.thunkModelBuilder(...)
at io.repaint.maven.tiles.TilesMavenLifecycleParticipant.orchestrateMerge(...)
at io.repaint.maven.tiles.TilesMavenLifecycleParticipant.afterProjectsRead(...)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.executeParticipants(...)
Key observations
- ✅ Using only Nisse → Works fine.
- ✅ Using only Maven Tiles → Works fine.
- ❌ Using Nisse + Maven Tiles together → Fails only on VS Code Java 1.46.0.
The same setup works perfectly with VS Code Java 1.45.0, suggesting a regression in 1.46.0 affecting how multiple Maven extensions are applied during model resolution.
Environment
| Component | Version / Info |
|---|---|
| OS | Ubuntu 24.04 |
| JDK | Eclipse Adoptium Temurin 21.0.8 |
| VS Code Java Extension | 1.46.0 (broken) / 1.45.0 (works) |
| JDT LS | 1.51.0.202510021738 (with 1.46.0) / 1.50.0.202509040211 (with 1.45.0) |
| Build System | Maven + Maven Tiles + Nisse |
| Nisse version | 0.6.1 |
Logs
- Vorherrschende Sprache
- TypeScript
- Sterne
- 2.3k
- Forks
- 547
- Ø Merge
- 5 Std. 36 Min.
- Gemergte PRs (30 T.)
- 10
Entwicklungsumgebung
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus redhat-developer/vscode-java
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
redhat-developer/vscode-java#4511 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
redhat-developer/vscode-java#4426 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 45/100
redhat-developer/vscode-java#4506 · 7 Kommentare · 4 Reaktionen ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 45/100
redhat-developer/vscode-java#4505 · 5 Kommentare · 2 Reaktionen ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 52/100
redhat-developer/vscode-java#4504 · 3 Kommentare · 1 Reaktion ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in redhat-developer/vscode-java
Ähnliche Issues
-
documentation
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
inu-appcenter/memorIN-frontend#106 ·
Maintainer antworten meist innerhalb von 1 Tag
-
kind/bug
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
Maintainer antworten meist innerhalb von 7 Tagen
-
[Bug] @deck.gl/arcgis dist import resolves to unpublished @deck.gl/core source path (9.3.11, 9.4.0)Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
CSCfi/sd-search-ui#145 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Add: Cbeebies pl SDOffencheck:passed streams:add
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
Maintainer antworten meist innerhalb von 1 Tag