[erlang-questions] fail_on_warnings, has it ever worked?

[Steve Vinoski]

On Wed, Oct 8, 2014 at 7:16 PM, Sam Tavakoli <sam@REDACTED> wrote:

> Hi
>
> Today I saw a project where the erl_opts in rebar.config had
> fail_on_warning instead of warnings_as_errors. Since I've never seen
> fail_on_warning before I googled it and among other results I found
>
> http://stackoverflow.com/questions/9343630/command-generate-not-understood-or-not-applicable
> .
> Where someone comments that fail_on_warning is deprecated in R16. I
> checked the R15B03-1 code and couldn't find anything related to
> fail_on_warning. I also tried it out in the shell but it didn't fail a
> compilation with warnings.
>
> The second interesting link I found is
> http://erlang.org/pipermail/erlang-questions/2011-March/057130.html
> where fail_on_warning is shown again in a different example and R14B is
> mentioned. I tried it out on R14B but it doesn't work either.
>
> So my question is, has fail_on_warning ever worked? If so, which release
> introduced it and when was it removed?


Assuming I'm reading the rebar code correctly, fail_on_warning was
rebar-specific, not something passed into the Erlang compiler. Rebar would
compile the file and if any warnings resulted and fail_on_warning was
enabled, it would fail the build.

--steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20141008/f394405a/attachment.htm>