| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| | |
Did not really know how to automate the testing for this, did it by
hand.
|
|/
|
|
| |
fixes #1469
|
| |
|
| |
|
| |
|
|\
| |
| | |
Allow exclusion of apps in cover
|
| |
| |
| |
| |
| | |
Adds a new option `{cover_excl_apps, Apps}` to exclude apps from coverage
analysis by name.
|
| |
| |
| |
| |
| |
| | |
on 19.x forward the compiler should now take into consideration the value
of the environment variable `ERL_COMPILER_OPTIONS` when deciding whether
or not to recompile a module
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Instead of a hard crash, display an error message indicating which app
failed.
We can't report the exact failure; only EDoc does it to stdout itself
and we can't capture it.
Pre/Post hooks are run properly despite the failure, as per escript and
compile providers.
|
|\ \
| | |
| | | |
See template local install same builtin as escript
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When the `new` command is run from a locally installed rebar3 (`rebar3
local install`), the builtin templates would be labelled as custom
because of directories.
This patch fixes it by splitting off the rebar3 priv dir from the user's
configured plugin path for custom ones, and introducing a new internal
label for builtins (since handling must remain different from escripts)
This fixes issue #819
|
| | |
| | |
| | |
| | | |
and clean up a bit
|
| |/
|/|
| |
| |
| |
| |
| | |
Requires changing a bunch of arguments for xerocopy since it
does not allow to rename while copying.
Lots of tests added
|
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes issue #880
May break backwards compat with projects that manually called the
dialyzer formatter, but we never documented or expected this to be
exposed.
|
|/
|
|
|
|
|
|
| |
This allows to reuse the code for any provider that formats source files
out to the user.
The option to configure it does remain compiler-centric for backwards
compatibility
|
| |
|
| |
|
| |
|
|\
| |
| | |
Type specifications and edocs improvements
|
| | |
|
| |
| |
| |
| |
| |
| | |
Includes improvments and function documentation for all modules (in
alphabetical order) up to rebar_core, and may have included more in
other modules as I saw fit to dig and understand more of the internals.
|
|\ \
| | |
| | | |
Improve merge of command line options and config options in CT
|
| | | |
|
| | |
| | |
| | |
| | | |
... before calling erlang:function_exported(ct_testspec,get_tests,1).
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Parse given test specs and add all spec- and suite directories as
extra_src_dirs in order to ensure that all these directories are
copied to the _build area and the suites are compiled.
Specs located in the project- or app root are explicitly copied to the
_build area in order to avoid recursive copying of the complete
directory tree.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This is a bugfix. It makes sure that the given path to a testspec is
translated so common_test will pick the spec from the _build
directory, and not from the source tree.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This is necessary in order to automatically get the testspec included
as an artifact (i.e. copied to the _build dir) in the case when it is
stored in another directory than 'test'.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: option 'spec' is not specifically handled when merging options
from the command line with options from rebar.config. Due to this, if
the config specifies a 'spec', then this will take precedence over any
'dir' and/or 'suite' on the command line.
This commit takes special care of all options that can be used to
select tests - meaning that if any of the options 'spec', 'dir',
'suite', 'group' or 'case' are specified on the command line, then all
'spec', 'dir', 'suite', 'group' and 'case' options in rebar.config
will be ignored.
|
| | |
| | |
| | |
| | |
| | | |
application modules will be added to the eunit test set automatically, no
need to consider them for inclusion in the test set separately
|
| | |
| | |
| | |
| | |
| | |
| | | |
stops the eunit provider from filtering out test modules based on the
file extension. previously, it was hardcoded to expect all test files
ended in `.erl`. this change allows for endings like `.lfe` and `.beam`
|
|\ \ \
| | | |
| | | | |
shell: don't crash apps that use release version operators
|
| | | |
| | | |
| | | |
| | | | |
Like for instance: {app, "0.1.0", '='}
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Fix regex match for ignored file
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The regex mistakenly matched too many files (any character followed by
an underscore) rather than only files starting in '._'
This properly escapes the expressions to work in all cases.
|
|\ \ \ \
| |/ / /
|/| | | |
add `get-deps` provider
|
| |/ /
| | |
| | |
| | | |
a no-op provider that depends on lock that is slightly more discoverable and user friendly
|
| | | |
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The option --single-branch was introduced in git version 1.7.10 and
thus rebar3 cannot fetch git dependencies on systems where earlier
git versions are install.
This commit will select other git clone commands if an earlier git
version is detected. If the git version cannot be determined rebar3
falls back on the previous behavior and uses --single-branch.
|
| | |
|
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| |
| |
| |
| | |
init_config, added unit tests
|
|/
|
|
| |
Fixes #1392
|
|\
| |
| | |
Add 'recursive' option
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The option {recursive,boolean()} can now be set pr directory in
'src_dirs' and 'extra_src_dirs', and on top level in the new
'erlc_compiler' option. Example config:
{erlc_compiler,[{recursive,false}]}.
{src_dirs,[{"src",[{recursive,true}]}]}.
This will cause recursive compilation within the "src" directory, but
not in any other directoires.
|
|\ \
| | |
| | | |
Unify different styles of missing_package error
|
| |/ |
|