[
https://issues.apache.org/jira/browse/SCM-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964862#comment-17964862
]
Olivier Lamy commented on SCM-671:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#876|https://github.com/apache/maven-scm/issues/876].
> Perforce provider Edit command incorrectly ignores working Directory
> --------------------------------------------------------------------
>
> Key: SCM-671
> URL: https://issues.apache.org/jira/browse/SCM-671
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.6
> Environment: maven 3.0.3
> Reporter: dwalling
> Assignee: Olivier Lamy
> Priority: Major
> Fix For: 1.7
>
> Attachments: PerforceEditCommandTest.java, patch
>
>
> When the working directory is something other than "." the perforce edit
> command does not include the relative path to the files actually being
> edited. For instance in the case where the directory structure is:
> pom.xml
> a/pom.xml
> a/foo.xml
> The command
> mvn scm:edit -f a/pom.xml -Dincludes=foo.xml
> will result in a failure because the method
> PerforceEditCommand.createCommandLine is assembling the path as if foo/.xml
> were at the top level.
>
> A second instance is the case where the directory structure is:
> pom.xml
> a/pom.xml
> a/b/pom.xml
> a/b/c/pom.xml
> The command
> mvn scm:edit -f a/pom.xml -Dincludes=**/pom.xml
> will result in only the top-level pom.xml being opened for editing, when it
> should open b/pom.xml and b/c/pom.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
