When the commit at
8c4a74a3ed
introduced a recursive search for build elements, it accidentally did so
using a function that accepts a regex for its match.

In doing so, if a behaviour or include had a name such as
`common_prefix` and that multiple other modules used the name
`common_prefix_<rest_of_name>`, all the other files would be seen as
dependencies to be checked in a directed graph.

This resulted in continuous re-checking of files that kept depending on
each others and blew the compile time up exponentially.

By using a delimitation on the regex (^<modulename>$), the build comes
back down to finding only the right files and becomes fast again.

Clear _build/bootstrap on each bootstrap run

update template moving maintainers into extras field

fix case clause when fetching hg dep

This should avoid common problems when upgrading across versions where
old code kind of messes up a lot of things and clearing _build keeps
being required.

update relx to 3.28.0

Remove unnecessary clauses in update_package/3

Update hex_core and add mirror_of repo config

- removed deprecated maintainers field from config template in
  rebar_prv_packages

Add --generator option for eunit

Add a --fail_fast switch to common test

bump erlware_commons to 1.3.1

re-expose download/3 for backwards compatibility in git deps related plugins

This switch aborts the rebar3 run after the first test failure is
reported.

Since Common Test does not support this feature and it can be useful for
interactive development (a demand from one of the teams I work with), I
decided to add the feature as an experimental CT hook.

The hook notices any test failure, and forcefully aborts the current
script execution, but only during the initialization phase of the next
test; this ensure that all other hooks for a post-test failure have the
time to do things right.

The CT logs _will_ be interupted, and hooks of all kinds may also
suffer.

Since this might be a bit tricky to support internally, I will be fine
with a review that results in "no, Fred. Please test this in a project
plugin first" or if I get told to use profiles to mature the feature
(i.e. `rebar3 as failfast ct ...`) with a custom hook declaration.

For issue https://github.com/erlang/rebar3/issues/1974
Revert "add rebar.lock to template gitignore"

This reverts commit 8fb8a91130.

This reverts commit 8fb8a91130.

For issue https://github.com/erlang/rebar3/issues/1974

Fixing systest to use up to date plugin

prevents some failures when running

implement mib_first_files support in rebar_compiler_mib

mostly copy/paste from rebar_compiler_erl

consider A-MIB imports from B-MIB:

rebar compile MUST FAIL if mib_first_files is ["mibs/A-MIB.mib"]
rebar compile MUST SUCCEED if mib_first_files is ["mibs/B-MIB.mib"]

Support ignoring entire modules in xref results

Fix pkg name during update by using pkg_name understood by hex

- Added support to rebar_prv_xref for filtering out whole module. A
  module may now be added to the list of xref_ignores in rebar.config or
  via -ignore_xref() module attribute
  - Added unit test for whole module filtering support to xref CT suite

Fix load order for custom project builders and parse transforms