apache / apache/maven-verifier

[MSHARED-1420] Emit warn in case the embedded launcher cannot be used

Open
#177 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Java
Stars
6
Forks
17
Avg merge
12m
Merged PRs (30d)
1

Description

**[Konrad Windszus](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kwin)** opened **[MSHARED-1420](https://issues.apache.org/jira/browse/MSHARED-1420?redirect=false)** and commented

Currently if some class loading exception happens while trying to initialize the embedded launcher it will transparent fall back to fork mode without emitting anything (https://github.com/apache/maven-verifier/blob/ef9d6fb01132b91998683268d51a75c9aca8e4b8/src/main/java/org/apache/maven/shared/verifier/Verifier.java#L1168). There should be at least a warning being emitted to clarify why the embedded launcher was not used.

This is particularly an issue from within an IDE where `mvn` cannot be found in the PATH.

---

**Affects:** maven-verifier-1.8.0

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at src/main/java/org/apache/maven/shared/verifier/Verifier.java around line 1168, where the embedded launcher fallback is handled. Trace the class-loading exception path and verify that a warning explains why fork mode was selected, while the existing fallback still works.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, tooling
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.