[0] Build and Release process

NOTICE: many servers have now disabled SSLv3 because of POODLE; to successfully build the project you will need maven version 3.2.5 or later.

These are the step to manually produce a new release version:

1. update all the pom.xml versions:

   mvn org.eclipse.tycho:tycho-versions-plugin:0.19.0:set-version -DnewVersion=1.0.2 -Dnotes-platform=url to a notes p2 repository

   *Learn more about the P2 repository here - https://github.com/OpenNTF/SocialSDK/wiki/Generating-a-notes-platform

2. create a full build (add -Dmaven.test.skip=true if necessary):

   mvn clean verify -Dnotes-platform=url to a notes p2 repository

3. save the assembled kit from the assembly\target\kit folder somewhere outside the project

4. create a partial build signed for central (this will not include domino build)

   mvn clean verify javadoc:aggregate gpg:sign install:install deploy:deploy

   *make sure your settings.xml has the server copied from sonatype

5. go to the sonatype dashboard

   https://oss.sonatype.org/#stagingRepositories

6. close the release and promote it

7. create a commit with all the changed files. this will be the commit to tag

8. update the version to the next snapshot version (i.e. released 1.0.2, upgrade to 1.0.3-SNAPSHOT)

   mvn org.eclipse.tycho:tycho-versions-plugin:0.19.0:set-version -DnewVersion=1.0.3-SNAPSHOT -Dnotes-platform=url to a notes p2 repository

9. manually check each pom.xml and MANIFEST.MF file to see that version numbers are all changed correctly

10. create a commit with the changed files

11. push the two commits to the repository

12. create a tag from the first commit, the one with the release number in the poms

13. create a release on github for the given tag, attach zipped&tarred kits saved at 3