Maven NEVER updates jars that have a non-snapshot version associated with them.
If you are "updating" jars then they MUST be called a.b.c-SNAPSHOT for Maven to notice the changes. Wayne On Tue, Sep 16, 2008 at 10:47 AM, Yaakov Chaikin <[EMAIL PROTECTED]> wrote: > Hi, > > I am using Maven 2.0.8. > > I have a custom remote maven repo with some JARs imported there. I > recently updated one of the JARs there, but noticed that when I built > on the client, no update was pulled from the remote repo and my local > repo still has the old one. Only after I erased the actual JAR from > the local repo, did it pull the file from the remote repo. > > I checked and all the files in the directory under (version) 1.0 of > that JAR file have new timestamps, so it's definitely new. > > I then tried to force by doing this: > mvn -U clean install > > That didn't bring in the new JAR. > > I then tried to edit the update policy and explicitely says "always": > <repositories> > <repository> > <id>central</id> > <name>FES Unclass Maven Repository</name> > <url>https://xxx</url> > <snapshots> > <updatePolicy>always</updatePolicy> > <enabled>true</enabled> > </snapshots> > <releases> > <enabled>true</enabled> > <updatePolicy>always</updatePolicy> > </releases> > </repository> > </repositories> > <pluginRepositories> > <pluginRepository> > <id>central</id> > <name>FES Unclass Maven Repository</name> > <url>https://xxx</url> > </pluginRepository> > </pluginRepositories> > > However, that didn't work either. > > Am I doing something wrong here? > > Thanks, > Yaakov. > > --------------------------------------------------------------------- > 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]
