This is the intended behavior. When you roll back and use a tag, Liquibase rolls back everything that changed after the tag. It does not remove the tag itself. The intent is that you would mark a set of changes with, for example, "Version1", and then deploy those changes. If you then came along a week later to apply a set of changes "Version1-1", and there was a problem with that deploy, you could then roll back to "Version1"
It would be helpful to file a bug with repro steps for the null pointer exception case you experienced.
Steve Donie
Principal Software Engineer
Datical, Inc. http://www.datical.com/
Steve Donie
Principal Software Engineer
Datical, Inc. http://www.datical.com/