How resource intensive is fingerprinting? What if I fingerprint all files that I build?
We deploy a lot of zipped archives instead of jars and wars in our JBoss instant. This way, we can generate various client configurations. However, it also means that the build assets can get moved around quite a bit, and I'd like someway of determining what build that file was associated with. Right now, I'm just fingerprinting the zipped archive, but it may be better if I fingerprinted all the files inside the archive before it is zipped. I can't imagine fingerprinting taking up a lot of resources, on a per file basis, but if I am fingerprinting hundreds of files per build, I can imagine it being a problem. What is your policy on fingerprinting files?
