apache / apache/maven

[MNG-5199] Return back org.apache.maven.user-settings and org.apache.maven.global-settings properties

Open
#6,989 6 comments 0 reactions 0 assignees View on GitHub
enhancement priority:major
Dominant language
Java
Stars
5.3k
Forks
3.1k
Avg merge
20h 42m
Merged PRs (30d)
297

Description

**[Karel Piwko](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kapy)** opened **[MNG-5199](https://issues.apache.org/jira/browse/MNG-5199?redirect=false)** and commented

According to discussion at http://maven.40175.n5.nabble.com/Maven-3-support-for-org-apache-maven-user-settings-td3261146.html, I'm sure there is a valid use case for the property:

Imagine following:

```
mvn -s setting.xml test
```

Surefire has no way to pass the path of the settings.xml in the spawned process. If the test in spawned process want to for example access remote repository defined in settings.xml, user has to specify settings.xml path in the test itself.

However, for the following:

```
mvn -Dorg.apache.maven.user-settings=settings.xml test
```

This system property can be passed to surefire configuration and propagated to the Surefire spawned process later on.

Having a system property removes duplication of the environment settings.

---

**Affects:** 3.0.3

9 votes, 10 watchers

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.