| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changes to how hex or packages may work in the future will necessarily
bring changes to the format of lock files.
This commit adds an optional framing for future lock files of the form:
{Version, LockList}.
<Whatever consultable attributes>
This format is supported such as the LockList is the current lockfile
contents, and will never have more information than it currently does.
Attributes can be whatever and are currently undefined.
Rebar copies will be able to:
- Keep using the core locklist (which avoids breaking the last year or
so of community libraries using rebar3)
- Warn when it runs an outdated copy in comparison to the lock file
- Automatically rewrite lock files in the format it supports
- Augment or parse files in a version-specific manner.
This changes the usage interface slightly, but is backwards *and*
forwards compatible.
|
|\
| |
| | |
Add secondary hook for rebar_prv_compile
|
| | |
|
| |
| |
| |
| |
| | |
erlc_compile, for before/after compiling .erls to
.beams, but before .app.src to .app
|
|\ \
| | |
| | | |
upgrade relx to 3.15.0
|
| | | |
|
|\ \ \
| | | |
| | | | |
Add test case for relx overlay vars
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Makes use of several var types: integers,
strings, binaries, binary strings and tuples.
|
|\ \ \ \
| |_|/ /
|/| | | |
Ignore unknown warning when dialyzer < 2.8
|
| | |/
| |/| |
|
|\ \ \
| |/ /
|/| | |
check top level config for minimum or blacklisted otps at start
|
|/ / |
|
|\ \
| | |
| | | |
add user-agent to http request headers
|
|/ / |
|
|\ \
| | |
| | | |
don't lose overrides in an app when installing plugins it uses
|
|/ / |
|
|\ \
| | |
| | | |
Fix bash completion regression (cf66dfd6ba) and make lopt strings more resilient
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
To prevent future mistakes like the broken string introduced in
cf66dfd6ba, put opening and closing " on separate lines in each
multi-line lopts string. This also allows for cleaner (smaller) diffs
when removing/adding a flag.
|
| | |
| | |
| | |
| | |
| | |
| | | |
cf66dfd6ba introduced a syntax error in the modified lopts string.
Without the fix, you'll provoke a shell error when trying to complete
`rebar3 ct --<something>`.
|
|\ \ \
| |_|/
|/| | |
don't strip the project apps when running `ct` with just a root suite specified
|
| | | |
|
|/ /
| |
| |
| | |
this ensures the project apps are compiled to `lib/` instead of `extras/`
|
|\ \
| |/
|/| |
Add module directory to include path
|
|/
|
|
|
|
|
|
|
|
| |
Several projects use an include path relative
to the project's root.
file:compile will look in three places for the include
files:
The current working directory
The directory where the module is being compiled
The directories given by the include option
|
|\
| |
| | |
add profile option to clean task
|
| | |
|
|\ \
| | |
| | | |
deduplicate default test set generated by `rebar3 eunit`
|
| | |
| | |
| | |
| | |
| | | |
this ONLY attempts to deduplicate test sets that are generated by
rebar in the absence of any user specified tests
|
|\ \ \
| | |/
| |/| |
local install and local upgrade
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
| | | |
add unstable install/upgrade instructions to readme
|
|/ / |
|
|\ \
| | |
| | | |
Rework README and CONTRIBUTING documents
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- The README is better targetted to newcomers and explains the basics of
the project: what it is, why use it, how to get started, where to find
more information. It looks less like a reference and more like a brief
overview of rebar3.
- Whatever looks like a list or reference manual material is expected to
be moved to the website
- Be clearer about the rebar3 project structure in CONTRIBUTING.md;
explain how to write tests, how to structure code, and so on.
- Added contributing section on bug reports, feature requests, etc.
|
|\ \ \
| |/ /
|/| | |
Display error message when bad config is loaded
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If a bad configuration file is submitted to rebar3 shell, display the
following error:
===> The configuration file submitted could not be read and will be
ignored.
And keep going otherwise rather than silently failing.
While crash-fast is usually a good mechanism, the shell so far is very
tolerant of failures from apps to boot and whatnot, so this feels
appropriate.
Fixes #1019
|
|\ \
| |/
|/| |
check at runtime instead of compile time for `file:list_dir_all/1`
|
| |
| |
| |
| |
| |
| | |
this is slower than the compile time check but i guess packaging rebars with
repos is still a thing and i think only the eunit and ct providers call it
anyways
|
|\ \
| | |
| | | |
change detection of valid modules for `eunit`
|
| |/
| |
| |
| |
| |
| |
| | |
`beam_lib:chunks(..)` needs a path to object code which, frustratingly,
`code:which/1` won't return for cover compiled modules. instead just
assume that if `code:which/1` doesn't return `non_existing` a module
is something we can run tests on
|
|\ \
| |/
|/| |
convert 'app' to 'application' in eunit_opts to match cmdline args
|
| | |
|
|\ \
| | |
| | | |
when using the `--file' argument to `eunit' paths were being converted
|
|/ /
| |
| |
| | |
into directory test arguments
|
|\ \
| |/
| | |
upgrade bbmustache and relx
|
|/ |
|
|\
| |
| | |
Remove triple brackets in bbmustache templates
|
|/
|
|
|
|
| |
Issues formerly were avoided by quoting atoms. Unquoting them created
unbalanced tags (`{{{name}}`) which were mistakes. This patch inserts
spaces to unconfused bbmustache.
|
|\
| |
| | |
upgrade relx to 3.12.0
|