https://issues.apache.org/bugzilla/show_bug.cgi?id=32526
--- Comment #6 from Mike Cepek <[email protected]> 2009-02-19 08:40:51 PST --- (In reply to comment #5) > there is no really nice way to do it, agreed. The problem is the additional > stiff only tarfileset can do (otherwise a filelist would do the trick). A filelist example would be helpful. As I mentioned in my recent user list thread, counting the number of files isn't feasible for many reasons (overhead, brittleness, doesn't solve the problem). The goal again is to fail if explicitly named files don't exist. This ensures that the archive being build contains all of the expected components. This error should (be allowed to) cause a build failure, rather than having the error occur later during product installation or run-time. I suggest that any solution that involves re-specifying the named files is not feasible due to brittleness (redundancy) and all the extra ant scripting. I believe there continues to be merit in this feature request. Since Resources and Resource Collections don't adequately address this problem, perhaps revisiting the initial request for additional attributes for <tarfileset> (and others) is appropriate. Or maybe someone can come up with a more elegant solution. If this problem is an issue for you too, please vote for this bug. Thanks. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
