maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Lea (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (WAGON-265) Let ftp wagon copy to a non-existing directory
Date Wed, 02 Sep 2009 06:39:41 GMT

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

Ryan Lea updated WAGON-265:
---------------------------

    Attachment: WAGON-265-wagon-ftp.patch

Attached patch to create non existing directories, during the initial cwd.

> 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

       

Mime
View raw message