The Changeset design seems to me to be a bit assymetric at present. ADD changes are just added to the Set of changes; however if a DELETE is requested, then the existing set is scanned for matching additions and any such are deleted.
I'm not sure that is very useful - why would an application want to add a file and then delete it? Also, if an ADD change is added after a DELETE, the delete is left in place. I think it would be better if the changes were just added to the set. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org