db-migrations-flyway-liquibase: fix dead Redgate/Liquibase doc links and back the lock-defaults claim with a real transcript

Several documentation.red-gate.com and liquibase.com URLs added in the previous commit had
since moved (Redgate restructured its docs under /flyway/reference/, Liquibase Pro pricing
moved to /pricing); this repoints them at the current, verified-200 pages. Also captures
docs/output/16-liquibase-lock-defaults-javap.txt, the trimmed javap output backing chapter
11's claim about Liquibase's default lock-poll and lock-wait settings, which chapter 11
previously asserted without a committed artifact to back it.

Co-Authored-By: Claude Sonnet 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Q6XdRjtsp4862EM44T7i9a
This commit is contained in:
2026-09-15 07:31:49 +00:00
co-authored by Claude Sonnet 5
parent 3908331431
commit 67e1b2d8a9
12 changed files with 48 additions and 13 deletions
+6
View File
@@ -87,6 +87,12 @@ helper — the tests assert the same numbers they print, so a transcript going s
| [`14-liquibase-oss-license-service.txt`](docs/output/14-liquibase-oss-license-service.txt) | [`LiquibaseLicenseServiceTest`](src/test/java/com/ankurm/dbmigrations/liquibase/LiquibaseLicenseServiceTest.java) |
| [`15-both-together-same-datasource.txt`](docs/output/15-both-together-same-datasource.txt) | [`BothTogetherTest`](src/test/java/com/ankurm/dbmigrations/BothTogetherTest.java) |
One file is the exception: [`16-liquibase-lock-defaults-javap.txt`](docs/output/16-liquibase-lock-defaults-javap.txt)
isn't produced by `mvn test` — it's the trimmed `javap -p -c -constants` output confirming
Liquibase's default lock-poll and lock-wait settings straight from `liquibase-core`'s bytecode
(see [chapter 11](docs/11-liquibase-locking.md)), captured by hand since there's no JVM assertion
that reads a compiled class's own constant pool.
## Findings worth the trip
- Flyway Community's `undo`, `diff`, `check`, `deploy`, `generate`, `model`, `prepare` and `auth` commands all **compile fine** and throw `FlywayRedgateEditionRequiredException` only at runtime — there is no working rollback in Flyway Community at all ([chapter 7](docs/07-why-there-is-no-undo.md)).