Really, you should never never update a released artifact... Did you put the updatePolicy inside the right repo? Namely the pluginRepository...
Cheers 2008/12/26 Stephen More <[email protected]> > On Fri, Dec 26, 2008 at 1:01 PM, Wendy Smoak wrote: > > On Fri, Dec 26, 2008 at 10:51 AM, Stephen More wrote: > >> In November, maven 2.0.9 downloaded a jar and a pom into my local > repository. > >> In the remote repository, the jar has not changed, but the pom has. > >> When I run maven today, the latest and greatest pom is not getting > downloaded. > >> Is this a bug ? How can I make sure I always get the latest pom version > ? > > > > If it was a released version then this is the default behavior. > > Released artifacts should never change and once it's in your local > > repo, Maven will not look for updates. If you know something has > > changed, deleting it from your local repo will cause Maven to go > > download it again. > > > > If it's a snapshot, then by default Maven should check once a day for > > updates. You can add -U on the command line to force it to check. > > > > If you want to override the default behavior, you can change the > > update policies for each repository (usually in settings.xml). > > This is a released plugin. > I added: > <releases> > <updatePolicy>always</updatePolicy> > </releases> > > to my pluginRepository but my old pom is still there. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
