Robert Scholte created MRELEASE-774:
---------------------------------------

             Summary: CLONE - mvn release:prepare fails with IOException and a 
write error (Access is denied)
                 Key: MRELEASE-774
                 URL: https://jira.codehaus.org/browse/MRELEASE-774
             Project: Maven 2.x Release Plugin
          Issue Type: Bug
          Components: prepare
    Affects Versions: 2.3.1
         Environment: Windows 7 both command prompt and cygwin using Perforce 
for SCM
            Reporter: Robert Scholte
         Attachments: maven-release-error.txt, 
mvn_release_output_x_client_env.txt, mvn_release_output_x.txt

When running

{{mvn release:prepare -Dusername=<perforce_user> 
-Dpassword=<perforce_password>}}

I get the errors:

* java.io.IOException: The filename, directory name, or volume label syntax is 
incorrect

* [ERROR] CommandLineException Exit code: 1 - Usage: add/edit/delete [-c 
changelist#] [ -d -f -k -n -v ] [-t type] files...
Missing/wrong number of arguments.

* [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:2.3.1:prepare (default-cli) on 
project root-project: Error writing POM: D:\Server\pom.xml (Access is denied) 
-> [Help 1]

The full output is attached.

Sometimes I also get the error:

* [ERROR] D:\Server\pom.xml - file(s) not in client view.

Though I created the client in the same location I'm running from, and I'm not 
sure that error is related to the others (as the others also occur when that 
one doesn't).

It's been suggested (on stackoverflow: 
http://stackoverflow.com/questions/10999403/maven-releaseprepare-ioexception) 
that the error has to do with my D drive being a mapped drive, though I don't 
think it is as it's not listed if I run {{subst}}. However, I think it _must_ 
be at least a partition on the same hard drive, unless my PC has three physical 
drives :P (work PC), but I guess that shouldn't make any difference to the 
program?

--
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

        

Reply via email to