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

["Falko Modler (JIRA)" <ji...@codehaus.org>]

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

Falko Modler commented on WAGON-265:
------------------------------------

I use 2.1 but creating non-existent parent folders does not seem to work (real ftp-server replaced with "someurl.com"):

{code}

I use 2.1 but creating non-existent parent folders does not seem to work:

Command sent: SYST

Reply received: 215 UNIX Type: L8 Version: SUNOS

Remote system is UNIX Type: L8 Version: SUNOS
Command sent: TYPE I

Reply received: 200 Type set to I.

ftp://someurl.com/mms/www/reuse-sites/mms-parent/ - Session: Opened
[INFO] Pushing c:\Develop\_dev\mms-modules\maven\exec-listeners-extension\trunk\target\site
[INFO]    >>> to ftp://someurl.com/mms/www/reuse-sites/mms-parent/../maven/exec-listeners-extension
Command sent: CWD /mms/www/reuse-sites/mms-parent/

Reply received: 250 CWD command successful.

Recursively uploading directory c:\Develop\_dev\mms-modules\maven\exec-listeners-extension\trunk\target\site as ../maven/exec-listeners-extension
processing = c:\Develop\_dev\mms-modules\maven\exec-listeners-extension\trunk\target\site as ../maven/exec-listeners-extension
Command sent: CWD ../maven/exec-listeners-extension

Reply received: 550 ../maven/exec-listeners-extension: No such file or directory.

Command sent: PWD

Reply received: 257 "/mms/www/reuse-sites/mms-parent" is current directory.

Command sent: CWD ..

Reply received: 250 CWD command successful.

Command sent: CWD ..

Reply received: 250 CWD command successful.

Command sent: PWD

Reply received: 257 "/mms/www" is current directory.

Command sent: CWD maven

Reply received: 550 maven: No such file or directory.

Command sent: MKD maven

Reply received: 550 maven: Permission denied.

Command sent: CWD /mms/www

Reply received: 250 CWD command successful.

Command sent: CWD /mms/www/reuse-sites/mms-parent

Reply received: 250 CWD command successful.

ftp://someurl.com/mms/www/reuse-sites/mms-parent/ - Session: Disconnecting
ftp://someurl.com/mms/www/reuse-sites/mms-parent/ - Session: Disconnected
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 47.461s
[INFO] Finished at: Fri Dec 09 20:56:09 CET 2011
[INFO] Final Memory: 33M/961M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:deploy (default-deploy) on project exec-listeners-extension: Error uploading site: Unable to create directory ../maven/exec-listeners-extension when processing c:\Develop\_dev\mms-modules\maven\exec-listeners-extension\trunk\target\site -> [Help 1]
{code}

This folder/path does already exist:
ftp://someurl.com/mms/www/reuse-sites/mms-parent/
But not the "maven" folder that needs to be created:
ftp://someurl.com/mms/www/reuse-sites/maven

The final site location sould be:
ftp://someurl.com/mms/www/reuse-sites/maven/exec-listeners-extension

Once I manually create the maven folder *and* it's subfolder exec-listeners-extension then site deployment works.

Important thing to note: The exec-listeners-extension module inherits from mms-modules-parent (direct parent) which inherits from mms-parent ("transitive" parent). I think that's why this relative navigation happens: [...]/mms-parent/../maven/exec-listeners-extension

> Let ftp wagon copy to a non-existing directory
> ----------------------------------------------
>
>                 Key: WAGON-265
>                 URL: https://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: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira