You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: conditionally enable OpenRewrite per module via marker files
Instead of always running OpenRewrite on all modules (which adds ~8 min
to every build), use Maven file-activated profiles to run it only on
modules with changed Java files.
Before the build, regen.sh creates .rewrite-enabled marker files in
modules that have modified Java files. The rewrite profile in parent/pom.xml
activates when this file exists, so OpenRewrite runs only where needed.
This approach is recipe-agnostic — adding new OpenRewrite recipes to
the profile requires no changes to the detection logic.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
0 commit comments