<settings>
<servers>
<server>
<id>apache-snapshots</id>
<username>your-apache-username</username>
<passphrase>ssh-passphrase</passphrase>
<directoryPermissions>775</directoryPermissions>
<filePermissions>664</filePermissions>
</server>
<server>
<id>apache.snapshots</id>
<username>your-apache-username</username>
<passphrase>ssh-passphrase</passphrase>
<directoryPermissions>775</directoryPermissions>
<filePermissions>664</filePermissions>
</server>
</servers>
</settings>
might work. If your apache username is the same as your local
username it can be ommitted. If you don't have an ssh passphrase it
can be ommitted. I didn't look to see how apacheds identifies the
snapshot repo, but you only need the entry for the id actually used :-)
hope this helps
david jencks
On Jul 27, 2007, at 12:11 AM, Emmanuel Lecharny wrote:
Hi,
I just have to deploy shared, but I don't have my usual computer. Can
someone provide me a settings.xml file ?
Thanks !
On 7/27/07, Enrique Rodriguez <[EMAIL PROTECTED]> wrote:
On 7/25/07, David Jencks <[EMAIL PROTECTED]> wrote:
we did a couple of experiments here and we think you need to:
set umask 2 in .bashrc. For non-interactive remote shell access
such as
through scp this is the file executed, not .bash_profile
in ~/.m2/settings.xml set
<directoryPermissions>775</directoryPermissions>
<filePermissions>664</filePermissions>
for each repository you are deploying to. We're not so sure
about the 2nd
point, but this works for me and we found that the source file
permissions
do have an effect on the target file permissions together with
the umask,
and these settings affect what maven presents as the source file
permissions.
The combination of both of these settings (.bashrc && settings.xml)
worked for me. Nice!
With just umask it didn't work.
Enrique
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
