You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/09/23 07:22:14 UTC

[jira] Updated: (MNG-888) occasional deployment failure - No such file or directory

     [ http://jira.codehaus.org/browse/MNG-888?page=all ]

Brett Porter updated MNG-888:
-----------------------------

    Component: maven-artifact

> occasional deployment failure - No such file or directory
> ---------------------------------------------------------
>
>          Key: MNG-888
>          URL: http://jira.codehaus.org/browse/MNG-888
>      Project: Maven 2
>         Type: Bug
>   Components: maven-artifact
>     Reporter: Brett Porter
>     Priority: Minor
>      Fix For: 2.0-beta-3

>
>
> When the deployment directory doesn't occur in the remote deployment repo, I have seen occasions where this fails, but on a subsequent attempt succeeds. This only seems to be at release time, so may be a case of wrong order of directory creation. It is over SCP.

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org