| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Add REBAR to environment before executing hooks
|
| |
| |
| |
| |
| |
| |
| |
| | |
REBAR will be set to the rebar binary which was executed and runs the
builds. Enables the use of the same binary for rebar invocations as
part of a pre or post hook like so:
${REBAR} escriptize
|
|\ \
| | |
| | | |
Some optimisation/refactoring using stdlib's functions
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
* Corrected regexp: `[x|y]` -> `[xy]`.
* Used an re:replace/4 option instead of multiple IOlist functions.
|
|\ \ \
| | | |
| | | | |
Add qualified name tests specification (see #118)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Augment 'tests' option of 'rebar eunit' command with ability to specify
tests to run using module-qualified names. This change also forced me
to change the way modules for coverage and for testing itself are
selected - module-qualified tests specifications are now taken into
consideration. Extend tests to cover new functionality. Update
dialyzer_reference accordingly.
|
|\ \ \ \
| | | | |
| | | | | |
Fix #176
|
| | | | |
| | | | |
| | | | |
| | | | | |
Extend CONTRIBUTING.md with regards to tests and credit.
|
|\ \ \ \ \
| |_|_|/ /
|/| | | | |
Add support for the Perforce VCS client via the "p4" tool
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This calls the 'p4' command-line tool to checkout and sync Perforce
trees. It involves significantly more special code in Rebar than
using 'git p4', but it eliminates the indirection of
Rebar->Git->Python->Perforce
|
|\ \ \ \ \
| |_|_|_|/
|/| | | | |
Namespaced types: fix build for 17.0
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
We use namespaced_types option to choose between dict() and dict:dict() types.
|
|\ \ \ \ \
| |/ / / /
| | | | | |
erlc: replace if expression with case of
|
|/ / / /
| | | |
| | | |
| | | | |
Motivated by the bug fix in 2c4d7d1.
|
|\ \ \ \
| |_|/ /
|/| | | |
erlc: fix typo in update_erlcinfo/3 clause
|
|/ / / |
|
| |/
|/| |
|
|\ \
| | |
| | | |
Error 'Command not found' when sname is used
|
| | |
| | |
| | |
| | | |
When a node is configured with -sname the REMSH_NAME_PART argument should be defined with using command 'hostname' but error occurs due extra space
|
|\ \ \
| |/ /
|/| | |
improve output when using `rebar shell`
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
attempt to emulate the behavior of
`erl -pa ebin -pa deps/*/ebin`
fix error messages and formatting issues of `rebar shell` by
shutting down and restarting the user subsystem in a mode more
hospitable to the shell than the simple user started when run
as an escript. emulate `error_logger` behaviour when the shell
is run via `erl`
add documentation of the shell command
limitations:
the erlang interrupt handler is not enabled when running as an
escript and there is no interface to re-enable it via erlang code.
this means `ctrl-c` will immediately exit the running process
unlike when running the shell via `erl`. `ctrl-g` is, however,
unaffected
the user subsystem is killed and restarted but not supervised. if
your code somehow relies on the user subsystem crashing and
restarting `rebar shell` may interfere with it's operation
|
|\ \ \
| | | |
| | | | |
Slim release support
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | | |
Make sure that eunit/qc_compile_opts works
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Document skip_apps=, apps=, and require_*_vsn
|
| | | | | |
|
| | |_|/
| |/| | |
|
|\ \ \ \
| | | | |
| | | | | |
rebar.app: remove superfluous quoting
|
| |/ / / |
|
|\ \ \ \
| | | | |
| | | | | |
Use lowercase for Windows drive name to resolve issue #250
|
| | | | |
| | | | |
| | | | | |
base_dir() returns already filename:absname()'ed path.
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
On windows, bootstrap.bat failed with next error.
Command 'escriptize' not understood or not applicable
This happens because the drive name in path got from rebar_utils:get_cwd() and base_dir(Config) are different case.
Made the drive name the same lowercase using filename:absname().
|
|\ \ \ \
| | | | |
| | | | | |
Extra commits for #129
|
| | | | | |
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Using the filename as a prefix is less readable and inconsistent with
the other log messages.
Before:
DEBUG: src/foo.erl depends on...
After:
DEBUG: Dependencies of src/foo.erl ...
|
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | | |
file_utils: properly report errors (fix #95)
|
| | | |
| | | |
| | | |
| | | | |
While at it, improve the error message printed by rebar_utils:sh/2.
|
|\ \ \ \
| | | | |
| | | | | |
Update THANKS
|
| | | | |
| | | | |
| | | | | |
Add my name to THANKS
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Fix #267 (code path regression)
|