$ cd ../target/release
|$ scp apache-ldap-api-<version>-* people.apache.org:public_html/shared-<version>/ |
|$ scp * people.apache.org:public_html/studio-<version>/ |
Since we are using Nexus for releases the release process is as follows (see also http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven).
Several things need to be correctly configured in your 'settings.xml' file located at '~/.m2/settings.xml'.
Here's a sample file:
Be aware that this phase will ask you about the release version of Studio modules.
We use a release number scheme that combines a version number and the date of the release:
An example of this release number scheme is '2.0.0.v20120111' (notice the '.v' string between the version and the date).
This is useful to verify your settings in ~/.m2/settings.xml (Nexus password and GPG key)
First, clean the previous test release attempt with:
Next, edit the root 'pom.xml' file to comment the 'repository' and 'application' profiles, as we don't want these modules (and their sub-modules) to be released in the Maven repository.
Also, edit the 'pom.xml' file of the 'Apache Directory Studio Libraries Plugins' module and remove the code related to skipping the deployment of 3rd party plugins:
Then, prepare the release with:
This creates a tag here: http://svn.apache.org/viewvc/directory/studio/tags/
This deploys the release to a staging repository. Go to https://repository.apache.org/index.html#stagingRepositories and close the staging repository.
This creates and deploys the site via ssh to people.apache.org/www/directory.apache.org/studio/gen-docs.
Edit the people.apache.org/www/directory.apache.org/studio/gen-docs/index.html file and add the deployed site to the list.
Move into the 'application' sub-module:
Edit the 'pom.xml' files of this sub-modules and all other (sub-)sub-modules to fix the parent version which still refers to the old version number (it was not modified during the release process because the 'application' profile was commented):
Run the following command to generate all the distribution packages:
Now, you have all the distribution packages available at '../target/release':
Start a 72h vote at the dev mailing list.
If the vote succeeds Studio project can be released.
Go to https://repository.apache.org/index.html#stagingRepositories and release the staging repository so all artifacts are published to Maven central.
Move the distribution packages to people.apache.org/www/www.apache.org/dist/directory/studio.