You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mark Struberg (JIRA)" <ji...@codehaus.org> on 2011/05/27 13:02:22 UTC

[jira] Work started: (WAGON-265) Let ftp wagon copy to a non-existing directory

     [ http://jira.codehaus.org/browse/WAGON-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on WAGON-265 started by Mark Struberg.

> 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
>            Assignee: Mark Struberg
>             Fix For: 1.0
>
>         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