"ERROR: OTP release 18 does not match required regex R15|R16|17"
When library authors incorrectly predict that a future OTP version will be incompatible with their code, it is exceedingly inconvenient not to have a way to turn the Erts, OTP version restrictions into warnings rather than fatal errors.
I encounter this fairly often as I usually do development with git master Erlang so am a version ahead of released OTP. Modifying the rebar.config files is not a useful solution as these restrictions are often embedded in dependencies too.
I propose that we add an option for rebar_require_vsn that turns the ?ABORT into a ?WARN and allows compilation to continue. Perhaps the existing -k or -f rebar options could have this effect?
Sounds reasonable to me, should be a simple patch.
@archaelus how about turning the ERROR into a WARN message and continue?
Yep - works for me. Are we talking about leaving the current ?ABORT and converting that to ?WARN if the flag is present, or dropping the current abort behaviour and making it always warn instead (i.e. unconditionally make the error non-fatal)? I like either but was proposing the former.
If the flag is present, it'll call ?WARN and not ?ABORT.
Treat vsn mismatch as warning if -f is passed
Here's a patch: #322.
Treat vsn mismatch as warning if -k/--keep-going