maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damian Nowak (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (SCM-527) Not enough information reported to enable troubleshooting
Date Wed, 02 Nov 2011 16:02:51 GMT

    [ https://jira.codehaus.org/browse/SCM-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282616#comment-282616
] 

Damian Nowak commented on SCM-527:
----------------------------------

If you need to save these these temporary files, use a work-around:
{noformat}
# while true; do chown root:root /tmp/*.commit; done
{noformat}


> Not enough information reported to enable troubleshooting
> ---------------------------------------------------------
>
>                 Key: SCM-527
>                 URL: https://jira.codehaus.org/browse/SCM-527
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-svn
>            Reporter: Kohsuke Kawaguchi
>
> SVN provider for Wagon often uses a temporary file to invoke svn.exe. Such a file is
immediately deleted, which makes it impossible for people to diagnose the problem when svn
operation fails.
> For example, in MRELEASE-332, the user cannot replicate the problem since he doesn't
know exactly what's in /tmp/maven-scm-248675112.commit. I just had a similar painful troubleshooting
session.
> I suggest you leave those temporary files around if the svn execution fails, so that
the user can just copy&paste the command line dump to the shell to retry the behavior.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message