Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Minor
-
Resolution: Won't Fix
-
Affects Version/s: 2.8
-
Fix Version/s: None
-
Component/s: Support Tools
-
Labels:
Description
when requesting ?describe for a not yet cached artifact which will fail content validation, the describe output does not include content validation failure as the cause of the not found.
I realize it may not be possible to store this reason long term when 404 is already cached but it would also be nice.
Log does print the reason...
jvm 1 | 2014-05-21 18:58:30,587-0300 INFO [qtp881188243-148] anonymous org.sonatype.nexus.proxy.repository.validator.DefaultFileTypeValidatorHub - File item central:/com/sonatype/baz-1.0.jar evaluated as INVALID during file type validation (validator=maven)
jvm 1 | 2014-05-21 18:58:30,587-0300 INFO [qtp881188243-148] anonymous org.sonatype.nexus.proxy.maven.maven2.M2Repository - Proxied item central:/com/sonatype/baz-1.0.jar evaluated as INVALID during content validation (validator=filetypevalidator, sourceUrl=http://repo1.maven.org/maven2/com/sonatype/baz-1.0.jar)
This looks like a case missed in NEXUS-5511