You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Jesse Kuhnert (JIRA)" <ji...@apache.org> on 2006/12/12 07:25:21 UTC
[jira] Created: (INFRA-1063) can't write to maven2 snapshot repo
can't write to maven2 snapshot repo
-----------------------------------
Key: INFRA-1063
URL: http://issues.apache.org/jira/browse/INFRA-1063
Project: Infrastructure
Issue Type: Bug
Security Level: public (Regular issues)
Environment: minotaur
Reporter: Jesse Kuhnert
Priority: Critical
When trying to deploy the latest snapshot version via "mvn deply" I'm getting permission denied errors trying to write to /www/people.apache.org/repo/m2-snapshot-repository/org/apache/tapestry/tapestry-project/maven-metadata.xml
The file is currently owned by "apbackup" user, which may/may not have to do with a valid backup process that may/may not have failed to release a file lock.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (INFRA-1063) can't write to maven2 snapshot repo
Posted by "Jesse Kuhnert (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-1063?page=all ]
Jesse Kuhnert resolved INFRA-1063.
----------------------------------
Resolution: Cannot Reproduce
Works for me now.
> can't write to maven2 snapshot repo
> -----------------------------------
>
> Key: INFRA-1063
> URL: http://issues.apache.org/jira/browse/INFRA-1063
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Environment: minotaur
> Reporter: Jesse Kuhnert
> Priority: Critical
>
> When trying to deploy the latest snapshot version via "mvn deply" I'm getting permission denied errors trying to write to /www/people.apache.org/repo/m2-snapshot-repository/org/apache/tapestry/tapestry-project/maven-metadata.xml
> The file is currently owned by "apbackup" user, which may/may not have to do with a valid backup process that may/may not have failed to release a file lock.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira