Re: Archiva Consumers question

On 10/16/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote: > ArchivaArtifactConsumer is an abstract-dealing-with-artifacts consumer. > RepositoryContentConsumer is for files. > > A file that isn't an artifact can be *.xml, *.sha1, *.md5, > maven-metadata.xml, bad content, poorly named content, etc. > >

Re: Archiva Consumers question

ArchivaArtifactConsumer is an abstract-dealing-with-artifacts consumer. RepositoryContentConsumer is for files. A file that isn't an artifact can be *.xml, *.sha1, *.md5, maven-metadata.xml, bad content, poorly named content, etc. Would it be better to state the phase/scan instead? Repository

Archiva Consumers question

I'm looking at... http://maven.apache.org/archiva/ref/latest/apidocs/org/apache/maven/archiva/consumers/package-summary.html What's the difference between ArchivaArtifactConsumer and RepositoryContentConsumer? (When is an artifact not considered repository content?) Thanks, -- Wendy

Re: svn commit: r584986 - /maven/archiva/trunk/archiva-web/archiva-webapp/src/main/java/org/apache/maven/archiva/web/repository/ProxiedDavServer.java

I traced this bug down to the the plexus-webdav code to this line. this.base.lookup( resource ).toAsciiString(); base is a URI object, resource is the relative path (String) to the resource. At first look, this appears to be a bug in the java.net.URI object!! (or at least an unexpected respons