[
http://jira.codehaus.org/browse/MRM-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97121
]
Wendy Smoak commented on MRM-243:
---------------------------------
I can reproduce it by deploying 1.0 of something, then deploying 2.0. The 2.0
jar is uploaded, but the metadata is not updated and the error is as shown
below.
Unfortunately, there is nothing in the log when this happens.
(If I change the groupId to one that isn't already in the repo, so that it has
to create a new directory, then it works fine. It seems to be unable to modify
the repository metadata file.)
$ mvn deploy:deploy-file -Dfile=test.jar -DartifactId=test -Dversion=2.0
-DgroupId=com.example -Dpackaging=jar -DrepositoryId=localhost
-Durl=dav:http://localhost:8080/archiva/repository/internal
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'deploy'.
WAGON_VERSION: 1.0-beta-2
[INFO] -------------------------------------------------------------------------
---
[INFO] Building Unnamed - deploy:deploy:jar:1-SNAPSHOT
[INFO] task-segment: [deploy:deploy-file] (aggregator-style)
[INFO] -------------------------------------------------------------------------
---
[INFO] [deploy:deploy-file]
Uploading: http://localhost:8080/archiva/repository/internal/com/example/test/2.
0/test-2.0.jar
[INFO] Retrieving previous metadata from localhost
[INFO] Uploading repository metadata for: 'artifact com.example:test'
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error installing artifact's metadata: Error while deploying metadata: Fai
led to transfer file: http://localhost:8080/archiva/repository/internal/com/exam
ple/test/maven-metadata.xml. Return code is: 507 Insufficient Storage
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 seconds
[INFO] Finished at: Fri May 25 23:45:22 MST 2007
[INFO] Final Memory: 3M/6M
[INFO] ------------------------------------------------------------------------
> 507 Insufficient Storage when deploying artifact with webdav
> ------------------------------------------------------------
>
> Key: MRM-243
> URL: http://jira.codehaus.org/browse/MRM-243
> 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: Magne Rasmussen
> Fix For: 1.0-alpha-2
>
>
> 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
