[ 
http://jira.codehaus.org/browse/WAGON-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189466#action_189466
 ] 

Ryan Lea commented on WAGON-265:
--------------------------------

I ran into the same issue and added a little code around the initial cwd to 
check if the directory existed.  If so, the directories are attempted to be 
created first, any failures will result in the call failing.

I had the intention of making this a configurable switch, although am not 
overly familiar with how to supply configuration to wagon providers.  As a 
result, there is a boolean to switch this feature on/off, which is on by 
default.  If someone is able to point me in the direction of how to provide 
configurable parameters to wagon providers, I'll happily also make it 
configurable, with the default being off.

Cheers

> Let ftp wagon copy to a non-existing directory
> ----------------------------------------------
>
>                 Key: WAGON-265
>                 URL: http://jira.codehaus.org/browse/WAGON-265
>             Project: Maven Wagon
>          Issue Type: Improvement
>          Components: wagon-ftp
>    Affects Versions: 1.0-beta-5
>            Reporter: Grégory Joseph
>         Attachments: WAGON-265-wagon-ftp.patch
>
>
> I usually configure my poms with such a site url : 
> {{ftp://hostname/path/to/www/projects/${artifactId}-${version}}}
> This actually works (as far as I can tell) with the ssh wagon. The ftp wagon 
> chokes, however, because the initial changeDir command is called with the 
> path above, and unlike when copying further files, it doesn't attempt to 
> create the missing directories.
> Is there a reason for this? Couldn't this be the default behaviour, or even 
> an optional one ?
> Alternatively, I'd have fancied a way to configure the site:deploy mojo to 
> tell it to pass something else than "." as destinationDirectory when calling 
> wagon.putDirectory ...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to