summaryrefslogtreecommitdiff
path: root/src/rebar_opts.erl
Commit message (Collapse)AuthorAgeFilesLines
* Issue #1416: Merge erl_files_first separately and avoid sorting.Thomas O'Dowd2017-05-111-0/+4
| | | | | | The order of the files listed in "erl_files_first" option is important and should not be sorted. By handling the merge similarly to mib_files_first, the sort order is preserved.
* Addresses https://github.com/erlang/rebar3/issues/1397Ted Burghart2016-12-051-33/+60
| | | | | | Ensures merged compiler options end up in the correct order to maintain profile precedence. Moves the merge functionality from rebar_opts:merge_opts/2 to a standalone function to ease extension and debugging.
* special handling of relx configs in profilesTristan Sloughter2015-11-261-0/+2
| | | | | | | | | | | Relx config need new values at the end of the list and profile additions prepended. So now in apply_profile in the case it is a relx config we prepend the config list. This does, however, mean that a profile release can not 'extend' a release defined in the default profile since the one being extended would have its definition after the profile release and thus relx would not be able to use its values for extending.
* do not sort mib_first_files during merge_opts, order must be keptTristan Sloughter2015-11-071-0/+4
|
* move opts functions to new module rebar_optsTristan Sloughter2015-09-011-0/+155