Tamás Cservenák created MRESOLVER-267:
-----------------------------------------
Summary: Align local repository implementation content types
Key: MRESOLVER-267
URL: https://issues.apache.org/jira/browse/MRESOLVER-267
Project: Maven Resolver
Issue Type: Task
Components: Resolver
Reporter: Tamás Cservenák
This is due legacy: resolver implements two LRMs: "simple" and "enhanced". The
API exposes this method:
{{org.eclipse.aether.repository.ArtifactRepository#getContentType}}
That in case of those two are inconsistent:
Simple LRM factory acts if passed in LocalRepository contentType is "" (empty
string) or "simple".
Enhanced LRM factory acts if passed in LocalRepository contentType is "" (empty
string) or "default".
BUT, once created, the
simple LRM.getRepository().getCotentType() reports "simple" -- OK
enhanced LRM.getRepository().getContentType() reports "enhanced" -- NOT OK
As using contentType returned from enhanced
LRM.getRepository().getContnetType() to create LRM will lead to error, as if
you look at factories, no factory will respond to "enhanced" content type
(hence, in this cases, hack is needed to override "enhanced" content type to
"default").
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
