Alan Sparks to be honest, I don't think we can say that version prior to 2.72 were JCasC compatible. Sure, some fields were configurable but the complete configuration was not possible.

Alex Earl did a great job at making sure that everything was configurable through JCasC.

We could advertise that if anyone was configuring email-ext with JCasC using a version prior to 2.72, then that configuration is no longer compatible.

This is due to the fact that:

1. JCasC team did a great job at trying to make as many plugin compatible as possible out of the box. This is why some fields were configurable
2. however, due to the legacy code in email-ext and the way some fields were configured before (through the UI and some hack in the Java code), Alex Earl had to refactor those elements.

I do understand  this is not really what you wish to ear Alan Sparks, but in the end, the plugin was not compatible with JCasC before 2.72.

This is the first version that JCasC is actually supported in email-ext. I don't know if there is a way to migrate the JCasC settings from a version where it was not supported to a version where it is. JCasC is very new to me. I implemented the changes required for the support, but I don't know much about JCasC itself.

OK, that's fair enough - been the second plugin in 2 weeks that required a jenkins.yaml redo because of JCasC support, so very surprised.  Since I'd found JCasC configs for this plugin on the Net was not aware that it wasn't "officially" supported.

Now that I know this is an issue I can deal with it.  Thanks.

I wish I knew more about JCasC to be able to come up with a better solution. My apologies that it caused you issues.

Thanks.  And thanks Adrien Lecharpentier for the pointer to the test config, that helped me change mine.