Maven import fails with Nisse + Maven Tiles on VS Code Java 1.46.0 (works on 1.45.0)

[lfvJonas]

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

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

2. Install the tile locally:

   mvn clean install

3. 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.1

   The 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:...
   

4. Set the MAVEN_OPTS environment variable using that output:

   export MAVEN_OPTS="-Dnisse.source.jgit.dynamicVersion=true -Dmaven.ext.class.path=${output form previous command}"

5. Verify that the project builds successfully on the command line:

   mvn clean install

6. Open vscode-issue-example-project in 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

vscode-1-46-0.log
vscode-1-45-0.log