| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
The raw log file is split into lines to check for errors.
However the logged message should contain newlines for easier reading.
|
|
|
|
|
|
|
|
|
|
|
| |
When REBAR_DEPS_PREFER_LIBS is set, dependencies with defined sources
are allowed to be searched for in system lib directory.
Under specific circumstances (i.e. in build environments without networking)
it is impossible to fetch deps locally. So, user needs a way to ask rebar to
search in system lib directory as well.
Signed-off-by: Matwey V. Kornilov <matwey.kornilov@gmail.com>
|
|
|
|
|
|
|
| |
The test program used to determine the word size of a crosscompiler is
crafted to return an error, so this changes the logic to expect an
error exit. If the crosscompiler actually compiles the test program
successfully, that would be remarkable and worthy of investigation.
|
|
|
|
| |
also add myself to THANKS
|
|
|
|
| |
Add myself to THANKS
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recent builds of LFE have stopped reporting compile errors when compiled with
rebar. Examination of this issue revealed that this was due to recent
changes in default LFE compile options.
The way that LFE handles compile options has slightly changed; ``verbose`` and
``report`` are now provided as defaults only if no other options are passed; if
other options are passed, these do not get set. As a result, we have stopped
seeing compile error info when building with rebar.
This change brings back the previous level of reporting that LFE developers had
when compiling their projects with rebar.
|
|
|
|
|
|
| |
Fix verbose level in global rebar config
Replace application:set_env on erlang:put
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* fix commit messages
* fix whitespace issues
* move internal helper functions to correct location
* unexport internal cross arch helper functions
* fix 18.0 time API compatibility
* fix Windows temp dir detection
* use correct helper function name
* use sh/2 instead of os:cmd/1
* match file:delete/1 result
* use logging macros
* fix typo
* fix Dialyzer warnings
* add Tony Rogvall to THANKS
* add missing termination clause
* os type must be win32, not windows
* match file:write_file/2 result
* document cross-arch variables
* simplify env_wordsize/1 (Thanks Fred Hebert)
|
| |
|
|
|
|
|
| |
If one is building Erlang from sources without making a proper release,
there may be an OTP_VERSION file in the root directory.
|
|\
| |
| |
| |
| |
| |
| | |
into RubberCthulhu-ct-groups-and-cases
Conflicts:
THANKS
|
| |
| |
| |
| |
| |
| |
| | |
Add option 'groups' to 'rebar ct' command. So the command "rebar ct suites=Suite1 groups=Group1,Group2,...,GroupN" is equal to "ct_run -suite Suite1_SUITE -group Group1 Group2 ... GroupN". It allows to run specified test groups in specified test suite with Common Test tool. Besides it is absolutely necessary to specify groups for running test cases which are included in these groups, otherwise init_per_group/2 and end_per_group/1 callbacks are not called by ct_run.
Add option 'cases' to 'rebar ct' command. So the command "rebar ct suites=Suite1 cases=Case1,Case2,...,CaseN" is equal to "ct_run -suite Suite1_SUITE -case Case1 Case2 ... CaseN". It allows to run one or more test cases in specified test suite. Currently rebar has an option 'case' which allows to run only one test case. The option case is remained for backward compability. It's suggested to consider the option 'case' as deprecaed and recommended to use 'cases' instead.
Updated help messages according to new command line options.
Add warning message when used deprecated options 'case', 'group', 'suite' in command "rebar ct".
|
| |
| |
| |
| |
| | |
The PLT that rebar will have dialyzer use is now created with make
build_plt - this commit explains that.
|
|\ \
| | |
| | |
| | | |
https://github.com/paulo-ferraz-oliveira/rebar into paulo-ferraz-oliveira-fix/xref_behavior
|
| | |
| | |
| | |
| | | |
American alternative to -behaviour()
|
| | | |
|
| |/
|/| |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If I pass an expression like: "$PWD/deps/local/lib" in the port env
string, it expands to "/deps/local/lib", (variable is expanded to the
empty string) but if I pass "${PWD}/deps/local/lib" it expands
properly. I found that confusing.
This was because we require environment vars to end with whitespace,
while I think requiring a non-word character would be sufficient, since
the variables can only contain word characters.
This changes the expansion system to recognize variables that are
terminated by non word characters.
This includes some fixes as per some comments by tuncer.
Fixes rebar/rebar#457
|
|
|
|
|
|
| |
ct_run has changed its config key from -ct_config to -config,
thus, -config key, used to specify app.config now must be
placed after -erl_args
|
|\
| |
| |
| |
| |
| |
| | |
irpab-fix_format_source
Conflicts:
THANKS
|
| |
| |
| |
| |
| |
| | |
Function format_source in rebar_deps.erl will fail on sources
like {rsync, Path} or {hg, URL} in rebar.config.
Add new function clause to match such source types.
|
| |
| |
| |
| |
| | |
This reverts commit 3c0f420c2a547cdb4f49348f19421513cf3a250e, reversing
changes made to 8f64e131846d53dbf8516f86270402465b7b37f8.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
kittee-ct_appconfig_fix
Conflicts:
THANKS
|
| |/
| |
| |
| |
| |
| | |
ct_run has changed its config key from -ct_config to -config,
thus, -config key, used to specify app.config now must be
placed after -erl_args
|
| |
| |
| |
| |
| |
| | |
Since rebar_deps:get_deps_dir/1 returns an absolute path,
lists:member(Deps, Parts2) will always return false, thus .test.spec
files in deps/ will not be ignored.
|
| |
| |
| |
| |
| |
| |
| | |
Loading .app, .app.src or .app.src.script returns now the value as per
the documentation (was wrapped in a list in some cases).
More places in the code detect .app.src.script and handle it.
|
| |
| |
| |
| |
| | |
This reverts commit 49930fe56656b46b6a35e4bcc92f4a18a402726a, reversing
changes made to 6e6b0fd43fe4e6ebf34808b9cf39a74b5d7946a2.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
into platinumthinker-color_in_logs
Conflicts:
THANKS
|
| | | |
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
exercises rebar/gpb integration
The bulk of these tests are written by Luis Rascão, hence he is the
author of this commit. As the committer, I have cherry-picked his two
commits 4c87bcd and ebb8182, from the feature/support_gpb_protobuf
branch in the git://github.com/lrascao/rebar repo, and have slightly
adapted it to fit this pluggable-proto-compilers-gpb branch.
Update the THANKS file
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
NineFX-erl-args-to-end
Conflicts:
THANKS
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Moves ct_extra_params to the end of the generated ct_run command.
This allows users to pass commands to the underlying emulator
using -erl_args. The included rt test demonstrates that it is
possible to pass an addtional option to ct_run and -erl_args at
the same time. Finally, the test executes in regular and verbose
modes because rebar constructs the ct_run command differently in
verbose mode.
|
| |
| |
| |
| |
| |
| |
| | |
- Use `cover' with QuickCheck testing
- Reuse the `cover_*' rebar.config options
- Refactor cover-related code to separate module (`qc_cover_utils')
for use with both `eunit' and `qc'
|
| |
| |
| |
| |
| | |
This reverts commit 3297ffec2c89c6b7135165b4bfaeaeb07167c33c, reversing
changes made to 0401debb3cf23d67affbe465a7a438049180a608.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
|
| |
| |
| | |
Add my name to THANKS
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* update files
* fix Dialyzer warning
* unconditionally enable info fil
* clean-up inconsistencies
* use term_to_binary compression
* use try...catch instead of case...catch...of
* do not write build info file if the graph is unmodified
* store info file as <base_dir>/.rebarinfo
* properly support list of compile directives
* fix regressions:
- Fix a bug in handling of files to compile first.
- If a file that is depended upon itself depends on other files, make sure
those are compiled first. While at it, rename variables for correctness.
Reported-by: David Robakowski
- Make sure that FirstFiles has no dupes and preserves the proper order.
- headers referenced via -include_lib() were not properly resolved to absolute
filenames
- .erl files found in sub dirs of src_dirs were not properly resolved to
absolute filenames
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|