Branch: refs/heads/xwiki-fix-deprecation Home: https://github.com/xwiki/xwiki-dev-llm Commit: bb59f9dcbcdfc666ac22ed61d04141a8bd3df995 https://github.com/xwiki/xwiki-dev-llm/commit/bb59f9dcbcdfc666ac22ed61d04141... Author: Vincent Massol <[email protected]> Date: 2026-09-27 (Sun, 27 Sep 2026) Changed paths: M README.md M xwiki/okf/index.md A xwiki/skills/xwiki-fix-deprecation/SKILL.md A xwiki/skills/xwiki-fix-deprecation/tools/deprecation-warnings.mjs A xwiki/skills/xwiki-fix-deprecation/tools/find-candidates.mjs M xwiki/skills/xwiki-legacy/SKILL.md Log Message: ----------- [Misc] Add the xwiki-fix-deprecation skill, to move callers off a deprecated API and retire it * New xwiki-fix-deprecation skill: choose a deprecated Java API (or get easy candidates proposed), check the replacement is equivalent, list every caller exactly from the javac deprecation warnings (plus the uses javac does not report), migrate the Java callers and their test stubs, verify, then hand the move to legacy to xwiki-legacy. Callers in Velocity templates, wiki pages, Groovy and JavaScript are migrated too, and verified by rendering them since nothing compiles them. * tools/find-candidates.mjs: ranks a repo's deprecated APIs by how easy they are to retire, with callers counted by name in xwiki-commons, xwiki-rendering and xwiki-platform (about 5 seconds). * tools/deprecation-warnings.mjs: groups the deprecation warnings of Maven build logs by API. * xwiki-legacy: point to the new skill for the caller migration; README and OKF index list it. 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