| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This lets a plugin define templates to be loaded:
$ rebar3 new
...
proper (plugin): A basic PropEr suite for an OTP application
...
$ rebar3 new help proper
proper:
plugin template (...)
Description: A basic PropEr suite for an OTP application
Variables:
name="suite" (...)
...
→ rebar3 new proper fakesuite
===> Writing test/prop_fakesuite.erl
In this case, proper is a fake template file I've put by hand in
_build/default/plugins/rebar3_proper/priv/<somename>/, meaning it will
only work as far as it's called from the project's root.
The priority order of plugins is now .config > plugin > built-in, such
that someone could ensure plugins do not crush their own private
templates, but also that custom or plugin templates do overtake built-in
ones. It used to be Built-in > .config only.
Templates are searched for recursively in the priv/ directory of
plugins.
|
|\ \ \ \
| |/ / /
|/| | | |
support temporary cdn change with HEX_CDN os var
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Fix wrong relative path resolution
|
| | | |
| | | |
| | | |
| | | | |
Tests both absolutes and relative paths.
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
schutm-wrong-paths
|
| | |/ / |
|
|\ \ \ \
| |/ / /
|/| | | |
A bad template index does not crash; shows warning
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This should fix #955
The test is implicit as a bad index previously silently crashed rebar3.
By adding the bad index to the `new` suite's files, we can show that
things keep running.
|
|\ \ \
| |/ /
|/| | |
Add support for total code coverage
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
symlink mib hrl output in apps `include' directories
|
| | | |
|
| | |
| | |
| | |
| | | |
this restores compatibility with rebar2 and erlang.mk
|
|\ \ \
| | | |
| | | | |
upgrade certifi to latest release
|
|/ / / |
|
|\ \ \
| |/ /
|/| | |
fix tupple merging for realsies.
|
| | |
| | |
| | |
| | | |
Full rewrite, code should be understandable now.
|
| |\ \
|/ / /
| | |
| | | |
tsloughter-tup_umerge
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Tup merge tests
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- proper segregation of comparison between tuple terms and non-tuple
terms. Guards weren't specific enough and that meant the wrong clauses
of guards would be triggered
- proper deduplication of entries in the list. An additional N passes
are required (we co-opt the reverse step to be more efficient) because
while the original lists:umerge easily removes dupes, this is
requiring more logic here since `[a,{a,b},{a,b,c},a,{a,b,c}]` is a
possible interleaving and we'd want `[a,{a,b},{a,b,c}]` -- comparison
of direct neighbours isn't enough.
|
|/ /
| |
| |
| | |
(the tests fail)
|
|\ \
| | |
| | | |
Fix a small bug in the MIB compiler when building dependencies
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When compiling a dependency with a MIB file the generated hrl file is left in
the root project directory in a file called "include". This has the perverse
effect of messing up the search path for include files causing any dependencies
with files in their "include" directory to fail to build after that.
|
|\ \ \
| | | |
| | | | |
Default to no eunit formatter if verbose specified
|
|/ / /
| | |
| | |
| | | |
The previous default meant that verbose output would not be emitted.
|
|\ \ \
| |/ /
|/| | |
fetch eunit_formatters config not from the command args but from the config
|
| | | |
|
|\ \ \
| |/ /
| | | |
auto-update the registry if a pkg isn't found, fail if it still isn't found
|
|/ / |
|
|\ \
| | |
| | | |
remove backward_compat entry from travis s3
|
|/ / |
|
|\ \
| | |
| | | |
special handling of relx configs in profiles
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
|\ \ \
| |/ /
| | | |
preserve attributes when copying files in rebar_utils:cp_r for unix
|
|/ / |
|
|\ \
| | |
| | | |
don't add a provider if the same namespace and name already exists
|
| | | |
|
|/ /
| |
| |
| | |
provider
|
|\ \
| | |
| | | |
Handle force flags in leading position
|
|/ /
| |
| |
| | |
The checking of flags and the parsing of arguments is separated up.
|
|\ \
| | |
| | | |
Ct output improvements
|
|/ /
| |
| |
| |
| | |
- eunit assert look better
- lager logs to the html logs
|
|\ \
| | |
| | | |
upgrade eunit_formatters to 0.3.1 for OTP18 bug fix
|
|/ / |
|
|\ \
| | |
| | | |
only add package list of versions to registry if it has the right build tool support
|
| | |
| | |
| | |
| | | |
support
|