what about permissions problems? anything in the logs (may need to turn up the level a bit)?
The other thought is whether the database has something in it that causes it not to work, but I don't think it's consulted first. I'm out of other ideas... really quite strange. - Brett On 29/02/2008, Brown, Carlton <[EMAIL PROTECTED]> wrote: > It populates just an empty 2.0.6 directory. The behavior is the same > whether that dir is pre-existing or not. I guess I could try installing > that artifact by hand and see what happens. > > I've also tried restarting tomcat as well. I'm not sure how I might go > about restoring the state other than that. > > > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 28, 2008 4:45 PM > To: archiva-users@maven.apache.org > Subject: Re: Archiva selectively failing to proxy one particular > artifact > > it works for me, so there must be a state problem rather than a bug in > the proxying related to that artifact. > > Do you have any content for that version in the managed repository? > > - Brett > > On 29/02/2008, Brown, Carlton <[EMAIL PROTECTED]> wrote: > > I have a strange problem where an Archiva instance absolutely refuses > > to retrieve one particular artifact from central under any > circumstances... > > it is /org/apache/maven/maven/2.0.6/maven-2.0.6.pom . I've verified > > that the instance can retrieve other artifacts, in fact > > maven-2.0.5.pom retrieves just fine, as well as other randomly > selected jars and pom > > files. It's only maven-2.0.6.pom that it fails on. I also verified > > that the file is in fact on maven central. > > > > When I say I'm testing it, I mean that I'm pointing a browser to the > > > archiva URL designating an artifact that is not yet proxied, for > > example > > http://myarchivahost/archiva/repository/myrepo/org/apache/maven/2.0.6/ > > ma ven-2.0.6.pom which returns a 404 error message. > > > > Also, I don't know if this is related or not, but the 404 message > > displays a munged, invalid URL: > > The following resource does not exist: > > > > http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.pom > > > > <http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.po > > m> > > > > > > Notice that the the context string "archiva" doesn't appear in the > > displayed URL, and neither does the repository name "myrepo". But > > since this behavior is reproducible with other well-formed URL's for > > > nonexistent artifacts, this may not be related to my problem at all. > > > > Thanks in advance... > > > > > > > > > > ----------------------------------------- > > ==================================================== > > This message contains PRIVILEGED and CONFIDENTIAL information that > > is intended only for use by the named recipient. If you are not the > > named recipient, any disclosure, dissemination, or action based on > > the contents of this message is prohibited. In such case please > > notify us and destroy and delete all copies of this transmission. > > Thank you. > > ==================================================== > > > -- > Brett Porter > Blog: http://blogs.exist.com/bporter/ > -- Brett Porter Blog: http://blogs.exist.com/bporter/
