I meant to say: I have recently tried to switch from using wagon-ftp when deploying (and publishing site) to using wagon-file because ftp does not support directory copying, but wagon-file seems to fail if the target directory already exists. I get the following error when deploying with wagon-file.
Caused by: org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Specified destination directory cannot be created: \\XRBUILD2\proximity\inhouse.snapshot\storage\com\xrite\xrite-commons\1. 17-SNAPSHOT This directory already exists as previous shapshots have been deployed here using ftp. Why would the file protocol give this error? -dh -----Original Message----- From: Dave Hoffer [mailto:[EMAIL PROTECTED] Sent: Sunday, October 22, 2006 3:48 PM To: Maven Users List Subject: [m204] deploy fails if directory exists using file I have recently tried to switch from using wagon-ftp when deploying (and publishing site) to using wagon-ftp because ftp does not support directory copying, but wagon-ftp seems to fail if the target directory already exists. I get the following error when deploying with wagon-ftp. Caused by: org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Specified destination directory cannot be created: \\XRBUILD2\proximity\inhouse.snapshot\storage\com\xrite\xrite-commons\1. 17-SNAPSHOT This directory already exists as previous shapshots have been deployed here using ftp. Why would the file protocol give this error? -dh --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
