[
http://jira.codehaus.org/browse/WAGON-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136493#action_136493
]
Benjamin Bentmann commented on WAGON-171:
-----------------------------------------
bq. fixed so the permissions are not set unless you ask them to be in wagon.
Brett, how will this fix the issue? If the permissions are specified and two
different people upload the same file, wouldn't it still crash for the later
deployment? Admittedly, I am not very familar with Wagon but your commit in
[r660818|http://svn.apache.org/viewvc?view=rev&revision=660818] doesn't seem to
handle this case so I just wonder.
> Cannot deploy files over existing files if someone else originally uploaded
> them.
> ---------------------------------------------------------------------------------
>
> Key: WAGON-171
> URL: http://jira.codehaus.org/browse/WAGON-171
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-ssh
> Environment: Desktop OS is Windows XP. Deploying to Solaris server
> using Tectia SSH2 Client.
> Reporter: Frank Russo
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 1.0-beta-3
>
> Attachments: File sharing issue with maven-deploy using wagon.txt
>
>
> On first deploy, everything works fine. On next deploy, if a different
> developer runs the command, the attached error occurs(see attached the
> original email posted to the Maven Users Mailing List.)
> The file is owned by the first developer, but has full rwx access (777). If
> developer 2 directly connects to the machine, they can do anything to the
> file, so it's not a Unix permissions issue...
--
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
