[
https://jira.codehaus.org/browse/SCM-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated SCM-671:
-----------------------------
Fix Version/s: 1.7
Assignee: Olivier Lamy
> Perforce provider Edit command incorrectly ignores working Directory
> --------------------------------------------------------------------
>
> Key: SCM-671
> URL: https://jira.codehaus.org/browse/SCM-671
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.6
> Environment: maven 3.0.3
> Reporter: Don Walling
> Assignee: Olivier Lamy
> Fix For: 1.7
>
> Attachments: patch, PerforceEditCommandTest.java
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
