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

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

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

   **[Dário 
Oliveros](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=oliveros)**
 opened 
**[SCM-208](https://issues.apache.org/jira/browse/SCM-208?redirect=false)** and 
commented
   
   I've been trying  to make a release by running 'mvn release:prepare', but 
got a warning saying that 'X' is an unknown file status.
   I noticed the release plugin runs the 'svn --non-interactive status' command 
internally which prints the status of working copy files and directories. Since 
one of the directories was fetched from a different svn repo thru 
svn:externals, its status is 'X' and it does not seem to be recognized by the 
release plugin. Therefore the outcome of 'mvn release:prepare' command is a 
build failure.
   
   
   ---
   
   **Affects:** 1.0-beta-3
   




> Status command doesn't support 'X' for svn:externals
> ----------------------------------------------------
>
>                 Key: SCM-208
>                 URL: https://issues.apache.org/jira/browse/SCM-208
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-svn
>    Affects Versions: 1.0-beta-3
>            Reporter: Dário Oliveros
>            Assignee: Emmanuel Venisse
>            Priority: Major
>             Fix For: 1.0-beta-4
>
>
> I've been trying  to make a release by running 'mvn release:prepare', but got 
> a warning saying that 'X' is an unknown file status.
> I noticed the release plugin runs the 'svn --non-interactive status' command 
> internally which prints the status of working copy files and directories. 
> Since one of the directories was fetched from a different svn repo thru 
> svn:externals, its status is 'X' and it does not seem to be recognized by the 
> release plugin. Therefore the outcome of 'mvn release:prepare' command is a 
> build failure. 



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

Reply via email to