On Sun, Sep 7, 2008 at 2:59 AM, Scott Carter <[EMAIL PROTECTED]>wrote:
> The artifacts are deployed from our Maven2 builds using WebDAV. So we use > a > config such as > > <snapshotRepository> > <id>snapshots</id> > <name>Internal Snapshot Repository</name> > <url>dav:http:// > <server>:8080/archiva/repository/snapshots/</url> > </snapshotRepository> > > I watched some of our builds and noticed that the timestamp of the > artifacts > takes the system time of archiva server (not the time stamp from the build > server), so everything should be in sync. The repository is configured to > scan for snapshots, and we see other snapshots being picked up. I have > also > looked at things like directory permissions and do not see any differences. > > > Does anyone have any other ideas on how to debug an issue like this? Is > there a way to force a scan of a single directory? You can do this by "touching" the directory so it gets scanned again.. In Linux for example, execute 'find [DIRECTORY_NAME] | xargs touch' in the command line then run the repository scanner for the repo again. HTH, Deng > > > On Fri, Sep 5, 2008 at 8:19 PM, Brett Porter <[EMAIL PROTECTED]> > wrote: > > > How is it deployed to the repository - via HTTP, WebDAV, or placed > directly > > onto the filesystem (eg, scp)? > > The only possibilities I can think of: > > - timestamp mismatches that cause it not to be scanned > > - the repository it is in is configured not to scan snapshots > > > > Cheers, > > Brett > > > > 2008/9/6 Scott Carter <[EMAIL PROTECTED]> > > > > > I am a newbie with Archiva and am having an issue with Archiva not > > > recognizing an artifact that is in our snapshot repository. We have a > > > build > > > that deploys it's artifact (a war file) to our repository. I know that > > the > > > artifact has made it to the repository because I can see it using urls > > such > > > as http://<server>/archiva/repository/snapshots/<path>/1.1.0-SNAPSHOT/ > > and > > > download it from there. But, if I use the browser from the main > archiva > > > page the latest version does not show up. The browser url looks like > > > http://<server>/archiva/browse/<path> . I can see older versions of > > this > > > build, but not the latest versions. Why would Archiva not register the > > > latest version even though it exists in the repository. > > > > > > This is not an issue of timing because the archive has been scanned > > several > > > times since the artifact has been added. I also do not see any obvious > > > errors in the archiva log files. Please help. > > > > > > Thanks - SC > > > > > > > > > > > -- > > Brett Porter > > Blog: http://blogs.exist.com/bporter/ > > >
