Howdy, you are conflating several things here: - timestamped snapshots are coming from remote (as locally installed ones are NOT timestamped), these snapshots can be resolved ONLY via metadata - artifact origin tracking: if artifact A was downloaded from repository R1, a subsequent build run on same local repo that does not have R1 defined (obviously, R1 cannot be central) will NOT have A reported as "available" only as it is present on disk (Maven2 did this, Maven3 fixed did this). - update policy is unrelated to both above
Hence, to me your question does not make sense. Let me reverse: what is your goal you want to achieve? T On Mon, Mar 25, 2024 at 9:21 AM Delany <delany.middle...@gmail.com> wrote: > Hi, > > I have a bunch of plugins like enforcer that I want to run with `mvn > validate -o` but I get > Cannot access *repo* in offline mode and the artifact > *artifact*:jar:2.4.1-20240322.141808-12 has not been downloaded from it > before > > There are snapshots of that artifact available in local maven repo, just > not that specific one. > I thought changing the updatePolicy to NEVER would solve this, but the new > enforcer (which now uses resolver) fails nonetheless. > > Is there a way to get resolver to treat all snapshots as equal in offline > mode? Is there a reason this isn't the default? > > Thanks, > Delany >
