)]}'
{
  "commit": "a0b229453461d64adf430b852459d372db88fd37",
  "tree": "b2f0d86929389198e702c97c9325ec70372449c0",
  "parents": [
    "5138cc25defbd6df4b6e296b4c7e3682cb26af2d"
  ],
  "author": {
    "name": "kubycsolutions",
    "email": "keshlam@kubyc.solutions",
    "time": "Wed Aug 13 00:17:15 2025 -0400"
  },
  "committer": {
    "name": "kubycsolutions",
    "email": "keshlam@kubyc.solutions",
    "time": "Sun Aug 17 18:04:50 2025 -0400"
  },
  "message": "For Xalanj-2711: Document approach, and issues, if we want to automatically\ninvoke xalan-test to smoketest builds (and to ensure source\npackaging gets current test results).\n\nAdd xalan-test invocation to integration-tests. Not quite cooked yet.\n\nMove xalan-test to verify phase?\n\nTry to update autobuild for new xalan-test via validate\n\nRevert \"Try to update autobuild for new xalan-test via validate\"\n... Seems I don\u0027t have permission for that. Sigh.\n\nThis reverts commit 6e8d520609cd74c34c8d7d7b49e10e23800a8ebf.\n\nDithering between \u003cant\u003e and \u003csubant\u003e tasks. There doesn\u0027t seem to be any advantage in the former; I had been hoping it would set current directory to avoid fixing defaults in xalan-test.\n\nIt isn\u0027t the prettiest, but I have found a way to cleanly build and run ../xalan-test from within the mvn build. That\u0027s highly desirable if we\u0027re going to ship the testcases with the source archive, since it captures the results of the latest run of the tests as evidence of acceptability. I am not yet addressing how xalan-test gets checked out, other than presumably throwing an error if it hasn\u0027t been.\n\nMaven execution ordering will mean distribution must be dependent upon integration-tests... or the conformance tests much be a separate module which distribution depends upon. WORK NEEDED.\n\nUpdate comments on current status of xalan-test integration.\n\nComments. ISSUE: Xalan-test is currently relying on our having run the package target to avoid version numbers in jarfile names, which keeps test from running successfully pre-package... but that\u0027s when it _wants_ to run, so package can copy most recent results into the source archive as documentation. Easiest fix would be to change xalan-test to use ../xalan-java/* (the only form of wildcard that Java classpaths support). Assuming we do decided to fix this; xalan-java\u0027s ant build did *not* always run smoketests.\n\nDisable the cross-call to xalan-test pending decision on that.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b440dfe9e18964f1fcf3d34326cd430b2f8a41e8",
      "old_mode": 33188,
      "old_path": "integration-tests/pom.xml",
      "new_id": "7ad88d501010e2af302c0a8a5de2b90c97b7c7f9",
      "new_mode": 33188,
      "new_path": "integration-tests/pom.xml"
    },
    {
      "type": "modify",
      "old_id": "0b69960483fc3fbf107a7ed63ff64632141457c1",
      "old_mode": 33188,
      "old_path": "pom.xml",
      "new_id": "9acded5314ae64d501052025f168d8d496fa14e2",
      "new_mode": 33188,
      "new_path": "pom.xml"
    }
  ]
}