First of thank for spending the time on a great product. I recently started using it for a project.
I’m guessing this has been discussed before, but a quick forum search didn’t turn anything up. I have a suggestion that would greatly improve the usability from my perspective, and I’m hoping you would agree.
Currently the documentation states:
Each changeSet tag is uniquely identified by the combination of the �id� tag, the �author� tag, and the changelog file classpath name.
I’ve confirmed that this is the case. I can see the rational behind it, but I’d like to make a suggestion.
Instead of a file path (which really has little to do with what the change is) the tool could be updated to take the changeset XML, normalize or canonicalize it so the commands are what’s interesting and not things like whitespace, and then calculate an MD5 or something similar off of that it could accomplish the same objective that I think the file path was serving.
Also as another suggestion, instead of considering a change in the file path (fingers-crossed normalized md5 over xml) as a new changeset, it would be nice if it just errored that the changeset is different than what was identified (id + user) before.