)]}'
{
  "commit": "b51475df723d7e3ccd1503adea03f593f796cf53",
  "tree": "0ea458a7705b693f00254b40196c51d5235ae2f7",
  "parents": [
    "4d0a8ee3f67accde467c26df2612294d2e344536"
  ],
  "author": {
    "name": "vrubezhny",
    "email": "vrubezhny@exadel.com",
    "time": "Thu Jan 09 17:25:11 2014 +0400"
  },
  "committer": {
    "name": "vrubezhny",
    "email": "vrubezhny@exadel.com",
    "time": "Thu Jan 09 17:25:11 2014 +0400"
  },
  "message": "[424131] JSDT Parser doesn\u0027t respect \"Enable Semantic Validation\" preference value\n\nProblem reported is made to respect Enable Semantic Validation preference value for the preferences, so the problems market as\nProblemSeverities.Optional (configurable problems) aren\u0027t reported in case of Semantic Validation is disabled.\nWith this fix the build validation and as-you-type validation (errpr/warning annotations) are showing the same results,\nnot configurable error/warning messages do not depend on the value of \"Enable JavaScript semantic validation\" preference value.\nAll the JUnit Test cases of DualParseSyntaxErrorTest and SyntaxErrorTest passed successfully.\n\nSigned-off-by: vrubezhny \u003cvrubezhny@exadel.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c780b3404b5b3a8ed88b88f11060cfa39574f338",
      "old_mode": 33188,
      "old_path": "bundles/org.eclipse.wst.jsdt.core/src/org/eclipse/wst/jsdt/internal/compiler/problem/ProblemReporter.java",
      "new_id": "baaf07fe1433d12cfa5b741900d3f98f747c5aa5",
      "new_mode": 33188,
      "new_path": "bundles/org.eclipse.wst.jsdt.core/src/org/eclipse/wst/jsdt/internal/compiler/problem/ProblemReporter.java"
    }
  ]
}