This is an automated email from the ASF dual-hosted git repository.
cstamas pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-resolver.git
The following commit(s) were added to refs/heads/master by this push:
new f168b40b7 RRF: Place remark about broken MRMs (#1820)
f168b40b7 is described below
commit f168b40b7e1cbccc6a1415f562d559cbb601fdef
Author: Tamas Cservenak <[email protected]>
AuthorDate: Wed Apr 8 20:17:14 2026 +0200
RRF: Place remark about broken MRMs (#1820)
* RRF: Place remark about broken MRMs
In certain cases, when group/virtual repositories are involved,
and MRMs leak random resources from member repositories,
document the possible circumvention.
* Apply suggestion from @cstamas
---
src/site/markdown/remote-repository-filtering.md | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/src/site/markdown/remote-repository-filtering.md
b/src/site/markdown/remote-repository-filtering.md
index 2577c4a93..7a6bf90d0 100644
--- a/src/site/markdown/remote-repository-filtering.md
+++ b/src/site/markdown/remote-repository-filtering.md
@@ -212,3 +212,9 @@ activity:
This leads to the following "constraints":
* "Maven Central" is asked only for those artifacts it claims it may have
(prefixes)
* "Some Remote" is asked only for allowed groupIds. If it publishes prefixes,
is even better: you will not ask for things it for sure does not have.
+
+## Broken Maven Repository Managers
+
+Users of certain Maven Repository Managers (MRM) reported issues with
filtering, breaking their builds. Usually the issue involves grouped/virtual
repositories where MRM leaks random resources from member repositories, like
the `prefixes.txt` is. Naturally, as MRM leaks one member prefixes file, and
Maven is "tricked" into belief it got proper prefixes file from remote
repository, builds will fail with message like **Prefix `$PREFIX` NOT allowed
from `$SERVER_ID`** (where `$PREFIX` is so [...]
+
+In this case, user should disable prefix discovery by using
`-Daether.remoteRepositoryFilter.prefixes.resolvePrefixFiles=false` user
property to prevent Maven attempting to resolve prefixes file from such broken
MRMs.
