Adding release signing profile to parent pom
Major repo layout and pom refactoring

This commit collects experimental release-engineering commits from the
fork github.com/dalaro2/titan, plus some additional commits from my
local repo.  I used a fork under the bogouser dalaro2 while
experimenting with release automation to keep my credentials separate
and reduce the likelihood of unintentionally pushing a "release" of
titan.  However, the dalaro2/titan commit history is noisy and
confusing because of all the fake releases and revert commits that I
made while testing.  The net changes are fairly small when expressed
as a patch between the common ancestor commit in titan03
(771fb4e10a2494c6569a210a16f8d3187aa4ae87) and the fork head, so I'm
collecting them into this new commit rather than pulling history from
the experimental fork.

The most important operational note about this commit relates to the
doc directory.  doc is no longer contained inside the titan repo.  doc
now points to the titan wiki repo using git submodules.  Furthermore,
all images used in the wiki that used to live in gh-pages now live in
the images folder inside the wiki repo.

There's a lot of documentation for git-submodules, but the cliffs
notes are something like:

* after cloning titan, do "git submodule update --init" to get doc
* when switching from a branch with submodule doc to a branch with
  the old doc directory, you may have to first "rm -rf doc"
[maven-release-plugin] prepare release 0.3.2
[maven-release-plugin] prepare for next development iteration
Add dist submodule for Berkeley JE
Made script to update gh-pages at release time

When the titan-site maven module is packaged with -Ptitan-release, it
will write a script target/site-scripts/gh-pages-update.sh.  This
script takes as its sole argument a release.properties file generated
by mvn release:prepare.  The script checks out a new copy of the repo
on branch gh-pages, then locally stages new javadoc, wikidoc, and a
new root index.html appropriate for the release version (the "release
version" is read from release.properties).  The script adds all its
changes to the git index but does not commit or push, leaving the
chance for the user to inspect and potentially modify its output.
Remove scm.tag=HEAD from pom.xml

This is a leftover from the 0.3.2 release
Merge branch 'titan03'

Merging release-engineering changes to pom.xml files and maven module
layout made during the 0.3.2 release.

Conflicts:
	doc
	pom.xml
	titan-all/pom.xml
	titan-berkeleyje/pom.xml
	titan-cassandra/pom.xml
	titan-core/pom.xml
	titan-es/pom.xml
	titan-hbase/pom.xml
	titan-lucene/pom.xml
	titan-test/pom.xml
Revert accidental omission of persistit module