Check policy settings of any repository definition from where problematic (snapshot) dependency is supposed to be fetched from. Maybe you'll reproduce issue locally once you clean your local repository (probably dependency artifact is there so you can build locally but hudson can not access repository where dependency artifact resides). Also if you're using alternate settings.xml to configure repository access there's a known bug<http://issues.hudson-ci.org/browse/HUDSON-4693>in hudson.
Regards, Stevo. On Mon, Oct 4, 2010 at 10:16 PM, Hilco Wijbenga <hilco.wijbe...@gmail.com>wrote: > On 4 October 2010 13:01, Anders Hammar <and...@hammar.net> wrote: > > Is it the snapshot metadata? Are you using Nexus 1.7.2 or earlier? If so, > > search the nexus mailing list for a patch or upgrade to Nexus 1.8.0. > > I'm not sure whether it's the snapshot metadata or not. I can't see > anything special there. How can I tell? Like I said, Maven doesn't > seem to be even asking Nexus for data. It just stops and complains it > can't find the POM. > > I've already upgraded to Nexus 1.8.0. Hudson is 1.379. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
