Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

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

未關閉
#4,214 5 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 4 天內回覆

@snjeza 已經在處理了。

開始於 2025年11月3日。

評估

這個 Issue 還沒有評估資料。

描述

bug Maven regression

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:

  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

主要語言
TypeScript
星號
2.3k
分支
547
平均合併
5 小時 36 分鐘
30 天內合併 PR
10

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

redhat-developer/vscode-java 的其他 Issue

查看 redhat-developer/vscode-java 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。