Hello Rob,
I am not confirm with the current implementation. If there is junk in the version number, the ordering is no longer deterministic (We had the concrete issue that we accidently have named one migration script to "1.2a")
I would suggest that the migration should log a warning if this is the case.
I also think, that the version 1.1.2-SNAPSHOT > 1.1.2 (which are currently treated as equal)
Hello Rob, I am not confirm with the current implementation. If there is junk in the version number, the ordering is no longer deterministic (We had the concrete issue that we accidently have named one migration script to "1.2a")
I would suggest that the migration should log a warning if this is the case.
I also think, that the version
1.1.2-SNAPSHOT
>1.1.2
(which are currently treated as equal)