After my discussion with @xPaw - we should abort the process if plugins from mismatched ASF version are loaded into the process. People doing that usually have no clue what they're doing, and since we always distribute official plugins in matched versions, this should be regarded as unsupported practice.
I might make it configurable behind --ignore-unsupported-environment just in case.
Will not apply to unofficial plugins, although I'm considering a warning if ASF loads plugin X that targets ASF version older than current.
Solution
-
Why currently available solutions are not sufficient?
-
Can you help us with this enhancement idea?
Yes, I can code the solution myself and send a pull request
Checklist
Enhancement purpose
After my discussion with @xPaw - we should abort the process if plugins from mismatched ASF version are loaded into the process. People doing that usually have no clue what they're doing, and since we always distribute official plugins in matched versions, this should be regarded as unsupported practice.
I might make it configurable behind
--ignore-unsupported-environment
just in case.Will not apply to unofficial plugins, although I'm considering a warning if ASF loads plugin X that targets ASF version older than current.
Solution
-
Why currently available solutions are not sufficient?
-
Can you help us with this enhancement idea?
Yes, I can code the solution myself and send a pull request
Additional info
No response