jamesfredley commented on PR #16011:
URL: https://github.com/apache/grails-core/pull/16011#issuecomment-5046900978

   @jdaugherty Update after the latest push (`c798c93778`):
   
   There is now a dedicated `legacyCommandSupport` flag (default **on**), 
separate from `cliAutoProvision`.
   
   - `cliAutoProvision` controls modern CLI companions only
   - `legacyCommandSupport` controls only the Grails 7 bridge 
(`grails-core-cli-legacy`)
   - Bridge provisions only when **both** are true
   - `legacyCommandSupport = false` keeps modern companions and disables only 
the bridge
   
   I kept the default on so already-published G7 command plugins keep working 
with zero user action after the #15948 split. The separate flag is the opt-out 
for people who want the modern CLI tier without the compatibility bridge.
   
   If the project decision is still "default off + loud detect/warn when legacy 
factories are present", that is a policy call and I can flip the default. The 
wiring is already split so that change is one convention flip, not a redesign.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to