Tamas Cservenak created MRESOLVER-687:
-----------------------------------------
Summary: Add Artifact/Dependency validation SPI hook
Key: MRESOLVER-687
URL: https://issues.apache.org/jira/browse/MRESOLVER-687
Project: Maven Resolver
Issue Type: Improvement
Components: Resolver
Reporter: Tamas Cservenak
Fix For: 2.0.8
Resolver treats GAV strings as opaquen, yet in some cases (ie. dependency
version set to some non existent property or property with typo) Resolver will
be asked to resolve that artifact potentially with incomplete (uninterpolated)
artifact. Resolver will obey (coordinates are opaque) and will return "no such
artifact".
This may lead to build error like "non resolvable artifact", while in fact user
had a typo in version property of a dependency.
Because resolver has no notion of "interpolation" and "placeholders" (it is
Maven doing this atop of resolver) a form of callback would be handy where
Resolver would have an extension point that is implemented in Maven invoked
before artifact/dependency is about to be resolved where Maven could throw
early error (not letting Resolver even try to resolve it) as Artifact was
"incompletely interpolated".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
