apache / apache/maven-invoker-plugin
[MINVOKER-377] Invoker plugin should sanitize environment it obeys
- Dominant language
- Java
- Stars
- 22
- Forks
- 35
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 7
Description
**[Tamas Cservenak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cstamas)** opened **[MINVOKER-377](https://issues.apache.org/jira/browse/MINVOKER-377?redirect=false)** and commented
Use case: let's use "split repository". All fine and dandy, you can set it in your `$HOME/.m2/settings.xml`. And your builds will use it. But, if you create IT using invoker, you have a problem:
* invoker:install observes "outer" build, and will _install the IT artifacts into split repository_
* invoker:run if use own settings, not using split, will fail to find anything in "it-repo"
Basically the env should be sanitized: install should produce local repo as run would use. As currently, there is not way to run ITs if split repo is used.
Similar to MINVOKER-372
---
No further details from [MINVOKER-377](https://issues.apache.org/jira/browse/MINVOKER-377?redirect=false)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the related MINVOKER-372 issue and tracing how invoker:install and invoker:run handle settings and local repositories. Reproduce the split-repository case described here. Done means install targets the local repository that run will use, allowing integration tests to find the installed artifacts.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100