[MPLUGIN-385] Clarify usage of scope "provided" for Maven artifacts with group id "org.apache.maven"

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

Since m-plugin-p 3.6.2 (MPLUGIN-370) all dependencies with group id `org.apache.maven` are supposed to be referenced with scope `provided`.
But once turning dependency `org.apache.maven:maven-archiver:3.5.1` to scope provided my ITs based on `org.apache.maven.shared:maven-verifier:1.7.2` are starting to fail with NCDF errors

```
java.lang.NoClassDefFoundError: Lorg/apache/maven/archiver/MavenArchiveConfiguration;
```

Is that a bug in the classloader with maven-verifier? What if I want to use a newer version than shipped with Maven like "maven-archiver 3.5.1"?
What about group ids starting with "org.apache.maven" like "org.apache.maven.shared"?

You can reproduce with https://github.com/apache/jackrabbit-filevault-package-maven-plugin.

---

**Affects:** 3.6.2

**Issue Links:**
- [MPLUGIN-370](https://issues.apache.org/jira/browse/MPLUGIN-370) check that plugin dependencies that are already exported by Maven are scope provided

- [MPLUGIN-386](https://issues.apache.org/jira/browse/MPLUGIN-386) Filter out maven-archiver and maven-jxr from scope warning

**Remote Links:**
- [GitHub Pull Request #56
](https://github.com/apache/maven-plugin-tools/pull/56)

0 votes, 5 watchers