ascheman commented on issue #606:
URL:
https://github.com/apache/maven-invoker-plugin/issues/606#issuecomment-4878042423
We keep hitting this with real plugin ITs — a concrete data point in case it
helps prioritise.
Setup: split local repo enabled globally
(`aether.enhancedLocalRepository.split=true`, `localPrefix=mvb-<branch>`).
Running `mvn clean verify -P run-its` on e.g. maven-jdeprscan-plugin:
- the outer build installs `maven-jdeprscan-plugin:3.0.1-SNAPSHOT` into
`<repo>/installed/mvb-<branch>/org/apache/maven/plugins/...`
- each invoker-forked IT build then cannot resolve it:
`maven-jdeprscan-plugin:3.0.1-SNAPSHOT/maven-metadata.xml was not found in
file:///.../.m2/repository during a previous attempt. This failure was
cached...`
- net result: every IT using the reactor plugin fails — ITs are simply
unrunnable with split on, exactly as described here.
Our only workaround is to move the `.mvn/maven.config` split settings aside
for the duration of the IT run and restore them afterwards, which defeats the
point of the per-worktree split.
Would a fix along the lines of "invoker:run inherits the same LRM/split
config that invoker:install observed" be acceptable? Happy to provide the full
repro and help test.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
