maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <>
Subject [jira] Closed: (WAGON-265) Let ftp wagon copy to a non-existing directory
Date Fri, 27 May 2011 18:34:22 GMT


Mark Struberg closed WAGON-265.

       Resolution: Fixed
    Fix Version/s:     (was: 1.0)

fixed in wagon-2.0-SNAPSHOT and deployed to our snapshot repos.

I used the following section to test it (beside a few new unit tests)



can you please also test if your scenario works now? txs!

> Let ftp wagon copy to a non-existing directory
> ----------------------------------------------
>                 Key: WAGON-265
>                 URL:
>             Project: Maven Wagon
>          Issue Type: Improvement
>          Components: wagon-ftp
>    Affects Versions: 1.0-beta-5
>            Reporter: Grégory Joseph
>            Assignee: Mark Struberg
>             Fix For: 2.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:
For more information on JIRA, see:


View raw message