“A rollback count of -1 is meaningless, please select a value greater than 0”
(Despite having the rollback tag defined).
Trying to workaround the problem I thought I’d provide that value as either being empty or a number above zero. Naturally liquibase complains:
“Cannot specify multiple rollbackXXX options, please select only one of rollbackTag, rollbackCount, rollbackDate”
Incidentally, is it common for liquibase users to create issues directly in your Jira, or should I run them through the forums first (as I have done now)?
It must not be picking up the tag name attribute and falling back to a rollback count that is defaulted to -1. If you could create an issue for it, that would be great.
Whether you create an issue or create a forum post, people do both. I plan on trying to make some guidelines, but haven’t gotten to that yet. For now, I would say that if it looks like an obvious bug, just create the issue directly. If you aren’t sure if it is user error or a bug, ask the question on the forum first.
