[
https://jira.codehaus.org/browse/WAGON-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285586#comment-285586
]
Falko Modler edited comment on WAGON-265 at 12/12/11 3:43 AM:
--------------------------------------------------------------
After Re-checking the logfiles, I can now see that wagon-ftp does try to create
the missing "maven" folder but fails with "Permission denied" because it tries
this in the wrong parent folder "/mms/www" instead of "/mms/www/reuse-sites".
This is because it executes CWD to the parent directory twice:
Command sent: CWD ..
I guess this is because the path already contains .. and something like an
automatic CWD .. might have been implemented to fix this issue (WAGON-265).
I will create a new bug ticket.
Edit: Done, see WAGON-363.
was (Author: famod):
After Re-checking the logfiles, I can now see that wagon-ftp does try to
create the missing "maven" folder but fails with "Permission denied" because it
tries this in the wrong parent folder "/mms/www" instead of
"/mms/www/reuse-sites".
This is because it executes CWD to the parent directory twice:
Command sent: CWD ..
I guess this is because the path already contains .. and something like an
automatic CWD .. might have been implemented to fix this issue (WAGON-265).
I will create a new bug ticket.
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
