[ 
http://jira.codehaus.org/browse/WAGON-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136578#action_136578
 ] 

Benjamin Bentmann commented on WAGON-171:
-----------------------------------------

bq. I think it will succeed if the permission is the same as before
No, to my knowledge, it will - by design - always fail if the user executing 
chmod is not the owner.
bq. but it makes sense to convert this failure to a warning.
Not sure about whether "warning" is really the appropriate log level. I mean in 
general, warnings indicate conditions that should most probably be fixed. But 
in this case, there is nothing to fix. The user simply doesn't own the file, 
that's not bad state. So I believe the warning would be another line of noise 
from Maven that users will learn to ignore. Hence I suggest to use "debug" 
level in case chmod failed. If there is something wrong with the permissions, a 
user will simply notice by failing to update the contents of the actual file 
being deployed.

> 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

        

Reply via email to