I've seen the same thing a couple of times with M3.0.2. Usually the -U works, but I've seen it not. This just happened again last night. The newer artifact was in Central (I manually searched), but the build would not find it.
I'm using Nexus, are you? I wonder if there is a setting on it to tweak? I was going to expire its cache and explore the issue further, but lost the thought while finishing the main tasks. On Mon, Feb 7, 2011 at 7:54 AM, wytten <[email protected]> wrote: > > Hi, > > I've been using alpha and beta versions of mvn3 for almost a year on the > same project, and it seems like only after upgrading to 3.0.2 on January 9th > that the behavior of the -U option has changed. Since that time I have had > to perform the following sequence several times: > > 1. mvn3 install -> fails due to an outdated library > 2. mvn3 -U install -> fails > 3. mvn2 -U install -> success > > Has something in fact changed? > > Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
