Mm maybe this is a teamcity issue.I've noticed that not all the agents (all on the same box) will fail but, when one does, it is stuck until I clear it's .m2 cache.
On Thu, Feb 12, 2009 at 8:33 AM, Tim <[email protected]> wrote: > I have a Teamcity setup w/ multiple build agents.One of my projects > depends on a SNAPSHOT release. > This snapshot release is now on version 24-20090211.152817-12.pom > version xxxx-4.pom had an error in the dependencies. > > I've noticed that every now and then an agent will not pick use the correct > pom and instead get "stuck" with old broken poms. > In my settings.xml I have: > > <repositories> > <repository> > <id>repo</id> > <url>http://central</url> > <releases><enabled>true</enabled></releases> > <snapshots> > <enabled>true</enabled> > <updatePolicy>always</updatePolicy> > </snapshots> > </repository> > <repository> > <id>public-snapshots</id> > <url>http://public-snapshots</url> > <releases><enabled>false</enabled></releases> > <snapshots> > <enabled>true</enabled> > <updatePolicy>always</updatePolicy> > </snapshots> > </repository> > </repositories> > > But it doesn't seem to work to refresh those agents. Even doing a -U > doesn't seem to help. > Instead I have to manually clean out the .m2 directory to get rid of this > issue. > Any ideas on what could be causing this? > > -- > > Doug Larson - "Instead of giving a politician the keys to the city, it > might be better to change the locks." > -- Joan Rivers - "Never floss with a stranger."
