I found it, thanks for your help - it really did help because the "wording" you used inspired a google query, which helped me find it.
Either way, this was what I was referring to (from the settings.xml reference): updatePolicy: This element specifies how often updates should attempt to occur. Maven will compare the local POM's timestamp (stored in a repository's maven-metadata file) to the remote. The choices are: always, daily (default), interval:X (where X is an integer in minutes) or never. So, since this timestamp never gets updated, it will try it again, and again, and again, etc.. Since I can't configure this policy "globally" for all repos, I'll just slowly, but surely, add each repository it's attempting to update from. Quintin Beukes On Sat, Oct 3, 2009 at 6:16 PM, Quintin Beukes <[email protected]> wrote: > It can't be with the setup. It looks for snapshot updates based on the > modification date of the SNAPSHOT's pom.xml in the repo. And because > this date doesn't update, because the new snapshot wasn't downloaded, > it looks for it again next time. > > The build setup is fine, because when I compile it, I only install it > in the local repo. The project I'm compiling though, has a > <repository> tag, so the updates are trying to fetch from these > repositories, but they're not there, because they're SVN trunk and not > released yet. > > > Further, >> Then change your snapshot repo update policy to never. However since > > This is what I was looking for. I'm very new to maven and I was > looking around at doing this. I found the element: <snapshotPolicy>, > but I don't see how to do this outside of a <profile>? > > Q > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
