)]}' { "commit": "cf2b06653bbee885dd684ecf97bbecccb654e5b8", "tree": "64ad78b13eee23b884413fecef9a8e60e5bda9f1", "parents": [ "8dcf4fceeda3f0c12419441a331fcfb45f6697d8" ], "author": { "name": "Brett Porter", "email": "brett@apache.org", "time": "Fri Aug 22 05:37:15 2014 +0000" }, "committer": { "name": "Brett Porter", "email": "brett@apache.org", "time": "Fri Aug 22 05:37:15 2014 +0000" }, "message": "[NPANDAY-598] re-instate previous fix\n\nThis is probably not the ideal way to address this issue - it seems like\nthe \"cache\" are actually collectors that should be scoped to the\nresolution request, and are storing instead of saving computation. The\nresolve cache is safe as it is only used to intersect with the resolved\nartifacts, but the dependency cache will grow as highlighted in this\nissue. These could be adjusted in future as a listener, or a processor on\nthe resolved artifacts, or something passed in to the resolution request,\nallowing these to become singleton objects again.\n\ngit-svn-id: https://svn.apache.org/repos/asf/incubator/npanday/trunk@1619669 13f79535-47bb-0310-9956-ffa450edef68\n", "tree_diff": [ { "type": "modify", "old_id": "603e88a9c43c7da728c7def7d533a32236250797", "old_mode": 33188, "old_path": "components/dotnet-executable/src/main/java/npanday/resolver/NPandayDependencyResolution.java", "new_id": "fde80cda84097d4616a6eddf888989cfbe632000", "new_mode": 33188, "new_path": "components/dotnet-executable/src/main/java/npanday/resolver/NPandayDependencyResolution.java" }, { "type": "modify", "old_id": "618902c4216d44c882e40bbd3daa980ea695b9c9", "old_mode": 33188, "old_path": "components/dotnet-executable/src/main/resources/META-INF/plexus/components.xml", "new_id": "0d8e27345db1203cfd7d0b53111cc02932d11247", "new_mode": 33188, "new_path": "components/dotnet-executable/src/main/resources/META-INF/plexus/components.xml" } ] }