apache / apache/maven-mvnd

two Java projects with the same pom configuration and modules.'mvnd clean package' in the second project will result in an error

Open
#1,349 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
Java
Stars
3.5k
Forks
250
Avg merge
16h 22m
Merged PRs (30d)
36

Description

### Affected version

Apache Maven Daemon (mvnd) 1.0-m7 windows-amd64 native client (b2ef5d81997adbcdb72dc8c5603722538fa641fe)

### Bug description

There are two Java projects with the same pom configuration and modules. After the first project has completed the 'mvnd clean package' command, executing 'mvnd clean package' in the second project will result in an error: D:\GitProjects\projectName>mvnd clean package
[INFO] Processing build on daemon 1d5e5f0f
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for com.ruoyi:ruoyi-modules-system:2.5.0: The following artifacts could not be resolved: com.ruoyi:ruoyi-modules:pom:2.5.0 (absent): com.ruoyi:ruoyi-modules:pom:2.5.0 was not found in https://maven.aliyun.com/repository/public during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of alimaven has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 5, column 13.............................

However, for the second project, executing 'mvn clean package' using Maven will be successful.

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the issue on Windows with two Java projects sharing the same POM configuration and modules. Run `mvnd clean package` in each project, then compare the failure with a successful `mvn clean package` run and inspect how the daemon handles cached parent-POM resolution. Done means the second mvnd build completes successfully without requiring a forced update.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.