Commit Graph
5 Commits
Author SHA1 Message Date
Algent 00834daccf docs: group Java migration documents 2026-09-14 13:10:40 +02:00
Algent 1de11db82d docs: add consumer migration checklist 2026-09-14 12:04:03 +02:00
Algent 367ecac68c docs: clarify slot refresh version requirement 2026-09-10 11:40:32 +02:00
Algent 92a1f82427 docs: answer whether consumers migrate twice
The notes told consumers what breaks on rebuild but not whether the
migration they are being asked to make is final. Without that, the
reasonable reading is that adopting the Java surface now buys a second
migration when the Scala runtime is removed later.

State the guarantee: the removal release drops the Scala-shaped entry
points and keeps their Java siblings, so one migration to the documented
surface is the whole cost. Name the one way to pay it twice, which is
aiming at a raw dev-jar class such as scalatraits.TRedstoneTile instead
of the stable IRedstoneTile capability interface. That is the mistake a
failing rebuild invites, and it fails at runtime in between.

Record two limits honestly: the guarantee covers the documented and
audited surface, which is why removal waits on adoption evidence rather
than source patches, and the source-layout move out of src/main/scala
changes no class, package or descriptor and so is invisible.
2026-09-09 16:46:23 +02:00
Algent 3a5f3a3b8d docs: add consumer recompile release notes 2026-09-09 15:58:22 +02:00