Hi Nathan,
I appreciate the response in the extreme.
The changeset was definitely re-executing though it's useful to
know that this causes the validation errors as well. One thing we
noticed, after changing the logging level to DEBUG, is that it looks
like checksums are being calculated on the SQL and not the declarative
statements, in particular alter table type changes, though, admittedly
this is somewhat conjecture. We also had a couple versions of
Liquibase reporting in. In one case we have 3.2.2, in another 3.1.1
and, in my system, ${project.version}. We've since rectified the
version issues, on the assumption that any SQL generation changes you
make in Liquibase will result in different checksums for the same changelog.
That said, it's just not clear why the changelog runs again in some
cases when EXECUTED is set, and the ID, AUTHOR and FILE have not
changed. One thing we were wondering about is that our ID's are the
name of the file, so have the .xml ending and wondering if that's
causing problems with a regular expression or something.
Thank you very much for any help you might have with this
additional information.
Sincerely,
Tim