[maven-release-plugin]  copy for tag messagesource-0.1
[maven-release-plugin]  copy for tag messagesource-0.2
[maven-release-plugin]  copy for tag messagesource-0.3
[maven-release-plugin]  copy for tag messagesource-0.5
[maven-release-plugin]  copy for tag messagesource-0.6
[maven-release-plugin]  copy for tag messagesource-0.6.1
Removed dependency on SpringSource repository

Switching the org.springframework dependencies from the Spring EBR to
their Maven Central equivalents removes the need to redirect to
different repository.
Updated SCM information for new github.com home
Configure maven-release-plugin to play nice with Git

The release plugin normally pushes everything during a release. If
something goes wrong or you missed a setting, you have to release with a
new version if you don't want to rewrite/rebase history. Switching of
the auto-push behaviour allows to make informed choices on when to
actually push a release.
Prepare POM for use with Sonatype OSS repositories

The POM requirements stated in the "Sonatype OSS Maven Repository Usage
Guide", need to be fulfilled, if a successful release in Central is the
goal. This means:

* Removing third-party repositories wherever possible
* Make use of the Sonatype OSS parent POM
Move back to -SNAPSHOT for re-release
[maven-release-plugin] prepare release messagesource-0.1-central
[maven-release-plugin] prepare for next development iteration
Merge branch 'maven-central-release' into HEAD

Moving to -SNAPSHOT version for re-release.

Conflicts:
	pom.xml
[maven-release-plugin] prepare release messagesource-0.2-central
[maven-release-plugin] prepare for next development iteration
Merge branch 'maven-central-release' into HEAD

Moving to -SNAPSHOT version for re-release.

Conflicts:
	pom.xml
[maven-release-plugin] prepare release messagesource-0.3-central
[maven-release-plugin] prepare for next development iteration
Reformat POM w/ tabs