Branch: refs/heads/fix/legacy-move-no-revapi-ignore Home: https://github.com/xwiki/xwiki-dev-llm Commit: 45269c3cf38663b2480e90faabb9f66aed231b10 https://github.com/xwiki/xwiki-dev-llm/commit/45269c3cf38663b2480e90faabb9f6... Author: Vincent Massol <[email protected]> Date: 2026-09-27 (Sun, 27 Sep 2026) Changed paths: M xwiki/okf/conventions/backward-compatibility.md M xwiki/skills/xwiki-legacy/SKILL.md Log Message: ----------- [Misc] A move to -legacy needs no Revapi ignore * backward-compatibility OKF: a main module wrapped by a weaving legacy module skips Revapi and the legacy module checks the woven jar, so moving an API to legacy adds no ignore; the only exception is a downstream consumer depending on the clean jar that actually fails. * xwiki-legacy skill: replace the "add the Revapi ignore" step accordingly, add the main-module xwiki.revapi.skip to the weaver setup, and record the two traps of re-adding members with an aspect (compile-time constants, via a constants interface + declare parents; Serializable classes without serialVersionUID). * backward-compatibility OKF: no Revapi ignore is ever added without the developer's explicit approval (the xwiki-legacy downstream step says so too). * Cuts: the per-item ignore recipe and the with/without-ignore stash check from the skill. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications