If you have a repo manager sitting between you and Maven central, you will be experiencing "strange things". At least with Nexus, but I would expect Artifactory as well. The reason is that Nexus has a not found cache, so it will not try to get the artifact if it's NFC (not found cache) thinks it doesn't exist, regardless if you use -U or not. A scenario I've run into: 1. Announcement mail of a new release is sent out. 2. You try to get the new release, but for some reason it hasn't been synced yet to Maven central. This will however put the requested artifact in Nexus's NFC (defaults to 24 hours IIRC). 3. You wait a few hours and try again. Maven will say it will not try to fetch the artifact, so you try with -U. But Nexus will not try again as the artifact is still in the NFC!
Do you follow? /Anders On Mon, Feb 7, 2011 at 19:21, wytten <[email protected]> wrote: > > Thanks for the reply. We are not using Nexus, we are using Artifactory. > When I have some time I will gather logs and post them here. > -- > View this message in context: > http://maven.40175.n5.nabble.com/Has-the-behavior-of-U-option-changed-tp3374270p3374705.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
