I think it's too late, "after creating build", if you don't have the CVS keywords in the files. (even then, to find the keywords in compiled .class files, you'd need $version$ etc. expanded in Strings, not just in comments)



So I think you need to do something before the build process, or at the start of it, etc.



In fact perhaps checkout time is the best time, to note what revision number is being checked out for each file, and you record those, for all the files you use in your build, in your own version manifest summary or something.



Even then, remember anyone can use "cvs admin", "cvs tag" etc. to change the revision numbers for an individual source file, after you've checked it out already, so the revision number you have may not be correct in the cvs "vaultfile" in the repository, anymore.