Ice,
It should be fairly easy to separate out the diffing code into a stand
alone tool and I would be more than happy to help with that.
However, I'd also love more details on your standard use case to see
if we couldn't integrate it into the library. I had originally
thought that by providing a means to designate a resource store
outside of the application path, the library would be able to perform
diffs between deployments of the application. For instance, if the
resource store were at /home/josh/resource_store and the application
were at /usr/bin/apache-tomcat/... then every time the application
was restarted/deployed, as long as the managed resources resided
within the same directory in the application, they could be diffed
against the versions stored in the resource store at /home/josh/
resource_store. Is this not the case?
Thanks for your time!
Joshua