How to publish snapshots yourself

[David Jencks]

After a bunch of help from dblevins and jdillon we got stuff set up  
so I can publish openejb snapshots.  Here are some hints so other  
committers can too.

1. log into people.apache.org and make sure your umask is 2
>umask
2

If not you need to add it to the appropriate profile for your shell.   
Most likely:

grep umask .*

to find the appropriate file and adding to it:

umask 2

Apparently a bug in mvn means that if you set umask to 022 no one  
else will be able to  deploy after you.

2. Add/modify your ~/.m2/settings.xml file so it includes

        <server>
            <id>apache-snapshots</id>
            <username>djencks</username>
            <passphrase>--------</passphrase>
            <directoryPermissions>775</directoryPermissions>
            <filePermissions>664</filePermissions>
        </server>
        <server>
            <id>apache.snapshots</id>
            <username>djencks</username>
            <passphrase>-------</passphrase>
            <directoryPermissions>775</directoryPermissions>
            <filePermissions>664</filePermissions>
        </server>

in the <servers> element, such as:

<?xml version="1.0" encoding="UTF-8"?>
<settings>
    <servers>
        <server>
            <id>apache-snapshots</id>
            <username>djencks</username>
            <passphrase>xxx</passphrase>
            <directoryPermissions>775</directoryPermissions>
            <filePermissions>664</filePermissions>
        </server>
        <server>
            <id>apache.snapshots</id>
            <username>djencks</username>
            <passphrase>xxxx</passphrase>
            <directoryPermissions>775</directoryPermissions>
            <filePermissions>664</filePermissions>
        </server>
    </servers>
</settings>

Currently openejb2 is using the non-standard id apache-snapshots  
instead of the standard apache.snapshots.  This is might get fixed soon.

3. If no one has messed up permissions on people.apache.org you can  
now push snapshots with

mvn clean deploy

Thanks!
david jencks