mirror of
https://github.com/GTNewHorizons/ForgeMultipart.git
synced 2026-11-13 00:47:52 +00:00
Algent
92a1f82427
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.