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:
- 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
- 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.