From commits-return-27948-apmail-directory-commits-archive=directory.apache.org@directory.apache.org Tue Oct 12 11:44:26 2010
Return-Path: 
Delivered-To: apmail-directory-commits-archive@www.apache.org
Received: (qmail 95999 invoked from network); 12 Oct 2010 11:44:26 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 12 Oct 2010 11:44:26 -0000
Received: (qmail 45051 invoked by uid 500); 12 Oct 2010 11:44:26 -0000
Delivered-To: apmail-directory-commits-archive@directory.apache.org
Received: (qmail 44969 invoked by uid 500); 12 Oct 2010 11:44:24 -0000
Mailing-List: contact commits-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help: 
List-Unsubscribe: 
List-Post: 
List-Id: 
Reply-To: dev@directory.apache.org
Delivered-To: mailing list commits@directory.apache.org
Received: (qmail 44961 invoked by uid 99); 12 Oct 2010 11:44:24 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Oct 2010 11:44:24 +0000
X-ASF-Spam-Status: No, hits=-1994.3 required=10.0
	tests=ALL_TRUSTED,HTML_FONT_LOW_CONTRAST,HTML_MESSAGE,MIME_HTML_ONLY
X-Spam-Check-By: apache.org
Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Oct 2010 11:44:20 +0000
Received: from thor (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o9CBi07x021111
	for ; Tue, 12 Oct 2010 11:44:00 GMT
Date: Tue, 12 Oct 2010 07:44:00 -0400 (EDT)
From: confluence@apache.org
To: commits@directory.apache.org
Message-ID: <32813435.22640.1286883840044.JavaMail.confluence@thor>
Subject: [CONF] Apache Directory Development > Guide to Directory Releases
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Auto-Submitted: auto-generated

    Guide to Directory Releases
    Page edited by             Stefan Seelmann

                         Changes (4)

            ...

            Releasing Apache Directory Projects can be involved.  This release guide will walk you through the process first by preparing your maven and gpg configuration then by leading you through the release of various subprojects at Directory. 

            There may be a few things you'll need to setup before you can release.  This release guide is geared to work off of a UNIX based system that has gpg installed. If you're using Windows then I feel for you :-) . 

We use Maven version 2.2.1 and JDK 1.6.0 to build all Directory subrojects even if they run on JDK 1.5. 

            ...

            h2. Maven Settings 

            You'll need a settings section for the Nexus and people.apache.org servers with a password or a path to the SSH key used.  Here's what my settings.xml file in \~/.m2 looks like: 

{noformat} 

            ...

                <!-- To publish a website using Maven --> 
    <server> 

                  <id>apache.directory</id> 

                  <username>username</username> 
      <privateKey>/Users/username/.ssh/id_rsa</privateKey> 

            ...

            h2. GPG Key 

            All subprojects are configured to deploy signatures for the artifacts uploaded to the repository.  The gpg plugin will check use the default gpg key for the user deploying the project with the release:perform directive of the release plugin.  This will prompt you for the passphrase for the default key.  If you do not have one setup the build will fail. 

You can generate and upload a PGP key to a PGP keyserver using the following commands: 

            ...

{note} 

            Make sure to have created the .pgpkey in your p.a.o/\~ directory and to have added your public key to the [KEYS|http://www.apache.org/dist/directory/KEYS] file. 

            See also [http://people.apache.org/~henkp/repo/faq.html#4] 

            {note} 

h2. Releasing Directory Projects and Making Release Announcements 

            |Releasing Daemon|[Releasing Daemon]| 

            | Releasing Skins | [Releasing Skins] |
| Releasing Checkstyle Configuration | [Releasing Checkstyle Configuration] |
| Releasing Shared | [Releasing Shared] |
| Releasing ApacheDS | [Releasing ApacheDS] |
| Releasing ApacheDS Manuals | [Releasing ApacheDS Manuals] |
| Releasing Studio | [Releasing Studio] |
| Releasing Studio Maven Plugin | [Releasing Studio Maven Plugin] |
| Releases Announcements | [Release Announcements] | 

Promoted by third party (update information may need to be sent) 

            ...

                            Full Content

        Introduction

Releasing Apache Directory Projects can be involved.  This release guide will walk you through the process first by preparing your maven and gpg configuration then by leading you through the release of various subprojects at Directory.

There may be a few things you'll need to setup before you can release.  This release guide is geared to work off of a UNIX based system that has gpg installed. If you're using Windows then I feel for you  .

We use Maven version 2.2.1 and JDK 1.6.0 to build all Directory subrojects even if they run on JDK 1.5.

Maven Settings

You'll need a settings section for the Nexus and people.apache.org servers with a password or a path to the SSH key used.  Here's what my settings.xml file in ~/.m2 looks like:

<settings>

  <servers>
    <!-- To publish a snapshot of some part of Maven -->
    <server>
      <id>apache.snapshots.https</id>
      <username>username</username>
      <password>********</password>
    </server>

    <!-- To publish a website using Maven -->
    <server>
      <id>apache.directory</id>
      <username>username</username>
      <privateKey>/Users/username/.ssh/id_rsa</privateKey>
      <filePermissions>664</filePermissions>
      <directoryPermissions>775</directoryPermissions>
    </server>

    <!-- To stage a release of some part of Maven -->
    <server>
      <id>apache.releases.https</id>
      <username>username</username>
      <password>********</password>
    </server>

  </servers>

  <profiles>
    <profile>
      <id>apache-release</id>
      <properties>
        <gpg.passphrase>********</gpg.passphrase>
      </properties>
    </profile>
  </profiles>

</settings>

Just replace your username, passwords and paths.  Note that the username and password is your Apache LDAP account.

You'll need to provide the passphrase in the settings.xml to access the gpg secret key installed on your host.  This is due to a bug with the passphrase prompt in the maven-gpg-plugin.  So unfortunately we must provide the passphrase in the settings.xml file in clear text.  This should change in the future when this bug is fixed.  Note that this passphrase is put into the release profile which we activate to properly sign and release the artifacts and poms via the release plugin.

GPG Key

All subprojects are configured to deploy signatures for the artifacts uploaded to the repository.  The gpg plugin will check use the default gpg key for the user deploying the project with the release:perform directive of the release plugin.  This will prompt you for the passphrase for the default key.  If you do not have one setup the build will fail.

You can generate and upload a PGP key to a PGP keyserver using the following commands:

gpg --gen-key
gpg --fingerprint
gpg --keyserver subkeys.pgp.net --send-keys <your key's id from last command>

Make sure to have created the .pgpkey in your p.a.o/~ directory and to have added your public key to the KEYS file.

See also http://people.apache.org/~henkp/repo/faq.html#4

Releasing Directory Projects and Making Release Announcements

 Releasing Skins 
 Releasing Skins 

 Releasing Checkstyle Configuration 
 Releasing Checkstyle Configuration 

 Releasing Shared 
 Releasing Shared 

 Releasing ApacheDS 
 Releasing ApacheDS 

 Releasing ApacheDS Manuals 
 Releasing ApacheDS Manuals 

 Releasing Studio 
 Releasing Studio 

 Releasing Studio Maven Plugin 
 Releasing Studio Maven Plugin 

 Releases Announcements 
 Release Announcements 

Promoted by third party (update information may need to be sent)

 Project 
 Reference 
 Contact 

 Studio 
 Open Source Rich client platform (RCP) applications 
 news@eclipse.org 

            Change Notification Preferences

        View Online
        |
        View Changes

Releasing Skins	Releasing Skins
Releasing Checkstyle Configuration	Releasing Checkstyle Configuration
Releasing Shared	Releasing Shared
Releasing ApacheDS	Releasing ApacheDS
Releasing ApacheDS Manuals	Releasing ApacheDS Manuals
Releasing Studio	Releasing Studio
Releasing Studio Maven Plugin	Releasing Studio Maven Plugin
Releases Announcements	Release Announcements