cstamas commented on PR #191: URL: https://github.com/apache/maven-resolver/pull/191#issuecomment-1253752583
My stance with this feature is somewhat aligned with this new feature https://issues.apache.org/jira/browse/MRESOLVER-274 when it comes to local repository. Simply put, if you share your local repository across many (unrelated) builds, you cannot be sure about the state of it (not to mention possible information leakage as well but let's not mix that in). But the "quality" of it may become questionable as well. For me, approach like Github Actions is the correct: you CAN cache local repo, but that cache is reused only for that very same project, nothing else, is not shared (for obvious reasons as well). On CI side, reuse of local repository should really be handled per job or job group, as ultimately you have the "nuke it and let MRM serve it up", but yes, it may create nice (hopefully internal, as MRM should be internal) traffic. Am on edge on this, but this PR is "too much", maybe then some post-resolve hook (component) and one needing it, may implement a component (and use it as build extension) that performs the task you need at the cost of overhead (checksum all resolved artifacts)? -- 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]
