It really depends on what you mean by "checked for updates"... SNAPSHOTS are checked for new versions of the snapshot artifact, and they are pulled down into your local repo cache to be used in this and future builds.
Depending on how your versions are declared, new versions of non-snapshot artifacts will also be checked for, pulled down, and used in the build as well. For example, Maven will look for new versions of plugins (eg Jar, War, etc) and use them unless you've "locked down" your versions. But Maven will not look for an updated version 1.5.2 if one already exists in your local repo cache. It is assumed that there is one and only one version 1.5.2 for a given artifact. Wayne On 2/9/08, Rahul Thakur <[EMAIL PROTECTED]> wrote: > From the following command: > > mvn -help > > I get this description for -U option: > > -U,--update-snapshots Forces a check for updated releases and > snapshots on remote repositories > > I would imagine both SNAPSHOT and releases are checked for updates :-) > > Rahul > > > Mark Struberg wrote: > > --- Rahul Thakur <[EMAIL PROTECTED]> schrieb: > > > >> And at times you can use the '-U' option to force an update check for > >> dependencies. > >> > > But again, this works only for SNAPSHOT dependencies, and not for > > 'released' versions. > > > > LieGrü, > > strub > > > > > > Machen Sie Yahoo! zu Ihrer Startseite. Los geht's: > > http://de.yahoo.com/set > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
