DO NOT REPLY [Bug 46088] Performance (speed) of large path(s) must be improved.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46088 Matt Benson changed: What|Removed |Added Target Milestone|--- |1.8.0 -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46088] Performance (speed) of large path(s) must be improved.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46088 Matt Benson changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #3 from Matt Benson 2010-01-29 07:51:25 UTC --- r808421 -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46088] Performance (speed) of large path(s) must be improved.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46088 --- Comment #2 from Aleksandar Susnjar <[EMAIL PROTECTED]> 2008-10-27 09:55:36 PST --- I *did* mention the problems you re-state ("... it can contain mutable pieces..."). And paths are presented as immutable themselves as there is no way to affect them from the script once they are created. I resolved my own problem by creating my own subclass which caches its own results but also pre-wraps its component resource collection for added iterator performance. I could share this source code, but this *would* cause problems if someone expects file system changes to be reflected after caching (I don't have such a problem). I like the idea of adding "cache" attribute to Path (and other resource collections). -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46088] Performance (speed) of large path(s) must be improved.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46088 --- Comment #1 from Matt Benson <[EMAIL PROTECTED]> 2008-10-27 07:53:57 PST --- Some of the resource collections do have a 'cache' attribute. Further, most places that accept paths should accept other resource collections, so a simple workaround for you would be to wrap your path in a union resource collection (cache defaults to true). Contrary to your assertion that paths, filesets, etc. are considered to be immutable, pre-Resource Collection versions of Ant worked by re-scanning for files (e.g. when getting the members of a fileset, of which it was and is possible to compose paths). When path was retrofitted as a resource collection it actually did originally cache results, leading to bug 41151 (a regression). As an additional measure we could propagate the 'cache' attribute directly to path to be passed to its underlying union (the original cut of path as a resource collection extended union and thus did support this attribute, but this was never released). -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46088] Performance (speed) of large path(s) must be improved.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46088 Aleksandar Susnjar <[EMAIL PROTECTED]> changed: What|Removed |Added OS/Version|Windows Vista |All Platform|PC |All -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.