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

Olivier Lamy commented on SCM-615:
----------------------------------

This project has moved from Jira to GitHub Issues. This issue was migrated to 
[apache/maven-scm#828|https://github.com/apache/maven-scm/issues/828]. 

> RemoveMojo to allow removing resources from version control
> -----------------------------------------------------------
>
>                 Key: SCM-615
>                 URL: https://issues.apache.org/jira/browse/SCM-615
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Improvement
>          Components: maven-plugin
>    Affects Versions: 1.5
>            Reporter: Paul Mackinlay
>            Assignee: Olivier Lamy
>            Priority: Major
>             Fix For: 1.6
>
>         Attachments: remove_mojo_patch.txt
>
>
> A patch file is included.
> Running the junit test shows that although the remove command fails, it is 
> not propagated to the mojo class.
> It is suggested that PerforceRemoveCommand.executeRemoveCommand() is changed 
> to rethrow CommandLineException as a ScmException.



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

Reply via email to