)]}'
{
  "commit": "fa6a7e30262bdbbe41775afbe9039fd3f5e2f08f",
  "tree": "0c2564a904485d9fc54c1b2a2435a1949c81f7aa",
  "parents": [
    "91ae30bd2bfaf4767d845759aad60972719c477f"
  ],
  "author": {
    "name": "Saša Živkov",
    "email": "sasa.zivkov@sap.com",
    "time": "Tue Jan 26 14:37:52 2016 +0100"
  },
  "committer": {
    "name": "Saša Živkov",
    "email": "sasa.zivkov@sap.com",
    "time": "Tue Jan 26 15:26:32 2016 +0100"
  },
  "message": "Add profile for signing artifacts\n\nPublishing artifacts to maven central requires signing. To make signing work I\nadded the following configuration in the $HOME/.m2/settings.xml:\n\n  \u003cprofiles\u003e\n    \u003cprofile\u003e\n      \u003cid\u003egpg\u003c/id\u003e\n      \u003cproperties\u003e\n        \u003cgpg.executable\u003egpg\u003c/gpg.executable\u003e\n        \u003cgpg.passphrase\u003e\u003c/gpg.passphrase\u003e\n      \u003c/properties\u003e\n    \u003c/profile\u003e\n  \u003c/profiles\u003e\n  \u003cactiveProfiles\u003e\n    \u003cactiveProfile\u003egpg\u003c/activeProfile\u003e\n  \u003c/activeProfiles\u003e\n\nas documented in [1]. Note that the executable could be named gpg or gpg2\ndepending on the platform.\n\nUse the following command to build, sign and stage the artifacts to the OSS\nSonatype:\n\nmvn clean deploy -DperformRelease\u003dtrue \\\n  -DaltDeploymentRepository\u003dsonatype-nexus-staging::default::https://oss.sonatype.org/service/local/staging/deploy/maven2/\n\n[1] https://gerrit-review.googlesource.com/Documentation/dev-release-deploy-config.html\n\nChange-Id: I4faede2f754656772320c326f4890e2c74a9dce0\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "49de1c2450f44923e74fa516bae239b45eed280b",
      "old_mode": 33188,
      "old_path": "pom.xml",
      "new_id": "e1ed478fba6db353aa7b385be8f169f7b9316ba8",
      "new_mode": 33188,
      "new_path": "pom.xml"
    }
  ]
}