Hi, > it is very difficult to reproduce this error, because downloading other > snapshots from same internal repository works, so repository settings > should > be fine (otherwise no downloads would work).
Is it always the same snapshot that cannot be downloaded correctly? Or do others show the same phenomenon? > in cases of failure of snapshot-download it manages to download the > meta-dataxxxx.xml to the local repository but nothing of the rest. > manually copying dependencies work, so file system permissions should be > fine. > another weird thing is, that when logging in as a different user and > executing 'mvn verify' works. > > the only way to get the problem fixed is by manually executing 'mvn > install' > on server under the same account which cruise control is run, so local > repository gets filled with respective dependency. this workaround is no > option to me because resolution needs to be done fully automatically. > > i know with above explanation i give you a hard time to figure out what is > going wrong that's it what i can see as symptoms. just wanted get some > help > where to search for the solution. maybe somebody has had same problems... How are the snapshots deployed to your repo? Do you use a repository manager for that or just simple file copy operations? Perhaps the corresponding metadata files get corrupted when two or more people try to deploy the same artifact at the same time...? If you say that the repository contents are on the same machine on which your CruiseControl instance is running: Have you checked the file permissions of the artifacts that cannot be fetched? Perhaps the permissions don't allow CruiseControl to access the corresponding files which could happen when a user deploys an artifact via file copy... HTH Thorsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
