Fork me on GitHub

Release Setup

These setup steps only need to be performed on a particular machine once.

Developers using Linux workstations can skip over the references to Cygwin. If using Windows, install cygwin, including Utils/gnupg and Net/openssh packages.

Create and install a SSH key

  1. Open a shell window. If using Windows, open a cygwin window.
  2. Use ssh-keygen to create an SSH key.

    ssh-keygen -t rsa -b 4096
    • Follow the latest steps and guides on the ASF website as you should NOT be using SHA1 and new keys MUST be at least 4096 bits.
    • Program defaults should be fine. No passphrase is required for the ssh key generation. The keys will be saved in ~/.ssh/id_dsa (private) and ~/.ssh/ (public).
    • See Authenticating By Public Key (OpenSSH) for a good description on why and how to perform this task.
  3. SCP your SSH public key ~/.ssh/ created in last step to ~/ on

    cd ~/.ssh  
    scp <your userid>  
    • You will be prompted for your password.
  4. Use ssh to login to

    cd ~    
    ssh <your userid>  
    • At this point, you will still be prompted for your password.
  5. Create a ~/.ssh folder in your home directory on and change its file mode to 700.

    mkdir ~/.ssh  
    chmod 700 ~/.ssh  
  6. Move or append ~/ to ~/.ssh/authorized_keys and change its file mode to 600.

    mv ~/ ~/.ssh/authorized_keys
    chmod 600 ~/.ssh/authorized_keys
    • Each public key in the authorized_keys spans only one line. For example: “ssh-dss AAAAB3NzaC1kc3MAAA ….. agBmmfZ9uAbSqA== dsa-key-20071107”
    • ‘#’ in the first column is a comment line.
  7. Exit out of this ssh session.

  8. Start a new ssh session. No login should be required this time due to the private ssh key on your local box matching up with the public ssh key in your home directory (~/.ssh).

    ssh <userid>
    • If you are still prompted for a password, then you have not set up the ssh keys properly. Review the steps above and ensure that all of the steps were followed properly. Or, maybe the instructions are still not quite right and they still need some adjusting. In that case, please update the instructions accordingly.*

Create a GPG key

  1. Open a shell window. If using Windows, open a cygwin window.
  2. Generate a key-pair with gpg, using default key kind (“RSA and RSA”) and keys size (4096).

    gpg --gen-key
    • The program’s default values should be fine. For the “Real Name” enter your full name (ie. Stan Programmer). For the “e-mail address” enter your apache address (ie. You will also be required to enter a “passphrase” for the GPG key generation. Keep track of this as you will need this for the Release processing.
    • The generated keys are stored in $HOME/.gnupg or %HOME%\Application Data\gnupg subdirectory.
    • Save the content in this subdirectory to a safe media. This contains your private key used to sign all the Streams release materials.
  3. Backup your home directory to another media ||

  4. Add your public key to the SVN repository. See the commands describe at the beginning of this KEYS file to perform this task. The gpg key-pair is used to sign the published artifacts for the Streams releases.

    gpg --list-sigs <Real Name> && gpg --armor -- export <Real Name>

    The KEYS file is updated via normal svn commit procedures. The one under w.a.o/dist/ has to be manually updated from svn.

  5. Submit your public key to a key server. E.g. SURFNET or MIT

  6. Following the instructions in and ask multiple (at least 3) current Apache committers to sign your public key.

Configure Maven

  1. Update your ~/.m2/settings.xml with the properties from Publishing Maven Artifacts
Licensed under Apache License 2.0 -