On Fri, Mar 6, 2026 at 5:07 AM 'James Nord' via Jenkins Developers < [email protected]> wrote:
> what about when someone does or doesn't want `optional` dependencies > included > Is that even a real use case? With a fresh `work/` dir, `mvn hpi:run` will load all plugins in test scope, in versions known to be compatible according to test coverage. If you want to test the effect of disabling certain optional dependencies, or test-scoped dependencies, just go ahead and disable them and restart. The `work/plugins/*.hpi.disabled` marker files will be respected. -- CONFIDENTIALITY NOTICE:_ This email and any attachments contain confidential and proprietary information of CloudBees intended only for the named recipient(s). Unauthorized use or distribution is prohibited. If you received this in error, please notify the sender and delete this email._ -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1YD5EMpBC-NSqRuOjgDz3Lqqc%2BU%3D8UkPE_q_28X9nhrg%40mail.gmail.com.
