{warning:Answering Questions} During the prepare goal's execution you'll be asked a number of questions. Please pay close attention to each question instead of hitting return everytime. In particular there is a question about what you want to call the tag. If you do not specify the correct tag which should be the release number 1.3.0 in this case, maven will use parent-1.3.0 instead without the *parent-* prefix. We don't want that so pay attention. Look here if you have any questions regarding what release tags should be for the studio subproject:

http://svn.apache.org/viewvc/directory/studio/tags {warning}

These commands will build, tag, sign, and deploy studio artifacts and their signature files to the repository. Check the following URLs during different stages of the process to see Maven at work:

5. Deploy the Site

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.

6. Generate the distribution packages

Move into the 'application' sub-module:

$ cd application

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):

$ text-editor-command pom.xml */pom.xml

Run the following command to generate all the distribution packages:

$ mvn clean install -Prelease

Now, you have all the distribution packages available at '../target/release':