slachiewicz opened a new pull request, #2112: URL: https://github.com/apache/maven-resolver/pull/2112
Since #2082, when an artifact is downloaded successfully, not-found markers that other repositories left for it in the same `.lastUpdated` file are expired, and each expiry is logged at WARN as a possible sign of a stale or spoofed not-found. That warning also fires in the ordinary case. Repositories are consulted in order and each one is touched before the next is tried, so with repositories `[A, B]` and an artifact that only exists on B, every first-time download writes A's not-found marker and then warns about expiring it, once for the POM and once for the JAR. On a fresh local repository that is one warning per file for every artifact served by a non-first repository. The manager now remembers which not-found markers it wrote during the current session. Expiring one of those is the normal fall-through between repositories and is logged at DEBUG; a marker left by a previous session still warns, since that is the case the expiry exists for. The expiry behaviour is unchanged in both cases, and the message no longer speaks of a "previous attempt" when the marker is seconds old. Two tests cover both cases. *This change was created with AI assistance.* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
