You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kohsuke Kawaguchi (JIRA)" <ji...@codehaus.org> on 2010/01/20 01:39:55 UTC
[jira] Created: (SCM-527) Not enough information reported to enable
troubleshooting
Not enough information reported to enable troubleshooting
---------------------------------------------------------
Key: SCM-527
URL: http://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.
-
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
[jira] Commented: (SCM-527) Not enough information reported to
enable troubleshooting
Posted by "Damian Nowak (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282614#comment-282614 ]
Damian Nowak commented on SCM-527:
----------------------------------
It's obvious those files should remain in /tmp! I now got {{Directory 'src/test/java/com' is missing}} failure on {{mvn release:prepare}} but I'm not able to tell why!
> 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
[jira] Commented: (SCM-527) Not enough information reported to
enable troubleshooting
Posted by "Damian Nowak (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (SCM-527) Not enough information reported to
enable troubleshooting
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282813#comment-282813 ]
Olivier Lamy commented on SCM-527:
----------------------------------
try
export MAVEN_OPTS="... -Djava.io.tmpdir=$HOME/tmp ..."
> 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