[ 
https://issues.apache.org/jira/browse/SCM-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962741#comment-17962741
 ] 

ASF GitHub Bot commented on SCM-716:
------------------------------------

jira-importer opened a new issue, #930:
URL: https://github.com/apache/maven-scm/issues/930

   **[Markus 
Karg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mkarg)** 
opened 
**[SCM-716](https://issues.apache.org/jira/browse/SCM-716?redirect=false)** and 
commented
   
   * Commands to reproduce problem:
     svn revert -R . && mvn scm:diff scm:status
   
   * Expected result:
     Does not find any differences to BASE.
   
   * Actual result:
     Reports "unknown Status for ${artifactId}.diff". This is really annoying, 
as ${artifactId}.diff actually is getting created by mvn:diff itself...
   
   Proposal solution:
   * Create that file inside $TEMP instead of the project's root. This not only 
solves the problem, but also potentially speeds up operations, as $TEMP often 
is located on faster (SSD or RAM) drives.
   
   
   
   ---
   
   **Affects:** 1.8.1
   




> mvn diff:status reports a file created by mvn:diff as new... :-(
> ----------------------------------------------------------------
>
>                 Key: SCM-716
>                 URL: https://issues.apache.org/jira/browse/SCM-716
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-svn
>    Affects Versions: 1.8.1
>         Environment: MVN 3.0.4, SCM 1.8.1, Win 7 Pro SP1 (64 Bit), JDK 
> 1.7.0_17
>            Reporter: Markus Karg
>            Priority: Minor
>
> * Commands to reproduce problem:
> svn revert -R . && mvn scm:diff scm:status
> * Expected result:
> Does not find any differences to BASE.
> * Actual result:
> Reports "unknown Status for ${artifactId}.diff". This is really annoying, as 
> ${artifactId}.diff actually is getting created by mvn:diff itself...
> Proposal solution:
> * Create that file inside $TEMP instead of the project's root. This not only 
> solves the problem, but also potentially speeds up operations, as $TEMP often 
> is located on faster (SSD or RAM) drives.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to