[
http://jira.codehaus.org/browse/MRM-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131245#action_131245
]
Andrew Heald commented on MRM-769:
----------------------------------
I've had to implement a workaround that effectively ends up using Archiva only
as a proxy.
The original Archiva repo is now accessed through Apache's mod_dav. I've
deleted my original Archiva repo and recreated it in the same name, but with a
different repo directory, and configured it to proxy the now mod_dav managed
repo.
All builds fine so far.
I note that there's discussion about replacing the WebDAV module in Archiva and
I thoroughly endorse this. :-)
> CLONE - 507 Insufficient Storage when deploying artifact with webdav
> --------------------------------------------------------------------
>
> Key: MRM-769
> URL: http://jira.codehaus.org/browse/MRM-769
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Environment: mvn 2.0.4, Windows Server 2003, Tomcat 5.5.17, Sun JDK
> 1.5.0_08, archiva HEAD
> Reporter: Andrew Heald
> Assignee: Joakim Erdfelt
>
> Sometimes when deploying with dav I get a "507 Insufficient Storage" error.
> The artifact (.../group/artifact/version/artifact-version.jar) gets deployed
> (with checksums).
> The metadata (.../group/artifact/version/maven-metatdata.xml) gets deployed
> (with checksums).
> It seems to happen when maven tries to upload the updated parent metadata
> (.../group/artifact/maven-metadata.xml). The checksums for this metadata
> deploys OK.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
