Permissions are not changed correctly when site is not deployed relative to its parent

[arteymix]

Affected version

3.21.0

Bug description

I have the following site layout for a parent/children project:

parent/
foo/
   foo-a
   foo-b

When running mvn -X site-deploy in the foo project, chmod is called only once on the parent project, leaving permissions untouched on foo, foo-a and foo-b.

Ideally, chmod should be called for every site being deployed, and not only once for the parent site.

But more concerning is that changing permissions recursively on the parent site is inefficient and likely dangerous as it may affect permissions on projects that are unrelated to the one being deployed.

[arteymix]

Actually, this is even worse, chmod is called on the parent for each module being deployed, so three time in the above example. None of these addresses the permission on the right module.

It seems like the right thing to do is to fix the directory that is subject to the permission changes.

[arteymix]

I'm using wagon-ssh-external version 3.5.3 for the deployment.