[GitHub] [maven-resolver] cstamas commented on pull request #297: [MRESOLVER-369] Introduce update check policy scope

["cstamas (via GitHub)" <gi...@apache.org>]

cstamas commented on PR #297:
URL: https://github.com/apache/maven-resolver/pull/297#issuecomment-1587741095

   PR is on-hold: testing shows that now when Maven "remembers" that Artifact cannot be downloaded, there is no way to get out of it (-U does not help, as policy is not applied to artifact by default anymore, before it simply went here as -U was "always", and implicitly cleared the error flags as well, so it "fixed" things). 
   
   IMO, this stems from the fact that policy ALWAYS was simply misused on Maven side (-U), and instead, "force update" on maven side may mean something else, like:
   * set update policy to ALWAYS
   * set cache not found/transfer to false
   * ... (what else?)


-- 
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: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org