Wagon nukes the permission bits of uploaded files.

Maybe wagon should use <filePermissions> only for new files
http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploy-ssh-external.html

Any news on this issue? This is now open for two months.

without patches it could be sitting here for long time until somebody volunteers

this is a result of chmod -Rf in the site plugin - wagon is doing the right thing. It keeps permissions on existing files copied individually.

in addition, the site plugin really shouldn't execute this - it should rely on the wagon to set them correctly. We can address issues in wagon where putDirectory doesn't set the permissions correctly. Simply removing the lines is probably the fix here.

Currently the site-plugin does this:

chmod -Rf g+w,a+rX

on the deployment directory. So it shoudn't remove any bits - just add them.

Perhaps you have a server section in your settings.xml that overrides the file permissions?
Something like this:

<server>
      <username>myUserId</username>
      <id>apache.website</id>
      <directoryPermissions>775</directoryPermissions>
      <filePermissions>664</filePermissions>
    </server>

1) The command "chmod -Rf g+w,a+rX" fails on HP-UX servers because "f", which is for silent output, is not an option.

2) I would prefer the file permissions, directory permissions, and chmod options be in the <distributionManagement><site> tag since the values are specific to the server. Each user should not have different values for the tags.

<project>
  ...
  <distributionManagement>
    <site>
      <id>projects.foo.com</id>
        <name>Foo.Com Project Site</name>
        <url>scp://projectsfoo.com/${project.artifactId}/${project.version}</url>
        <directoryPermissions>775</directoryPermissions>
        <filePermissions>664</filePermissions>
        <chmodSilentOption/> <!-- Defaults to "f" -->
        <chmodRecursiveOption/> <!-- Defaults to "R" -->
      </site>
    </distributionManagement>
</project>

Command-line zip/unzip preserves permissions and remotely the command line unzip is used. So the problem is really with wagon, the x bit gets lost when zipping up the site. The rest is just a question of setting up the server and umask settings.