summaryrefslogtreecommitdiff
path: root/rebar.config.sample
Commit message (Collapse)AuthorAgeFilesLines
* Optionally look for ct .spec files in the ct_dir that was specifiedLuis Rascão2016-03-141-0/+4
| | | | | | | | | | | | | Allow to change existing behaviour which is to find all .spec files recursively in the current working directory through a new rebar.config option: {ct_search_specs_from_test_dir, true} This is confusing since the user explicitly stated the location for his spec files and negates the possibility to have different spec'ed suites for different environment. Also fix the node name generation on the ct test run, append a random number that will reduce chances of name collisions on epmd.
* Drop support for `shared` pltJames Fish2015-06-061-3/+1
|
* dialyzer: nest dialyzer options to match rebar3Tuncer Ayaz2015-05-221-13/+12
| | | | | | | | | | | | | | | {dialyzer, [ %% Store PLT in ~/.rebar/plt (Default) {plt_location, shared}, %% Store PLT locally inside the project in .rebar {plt_location, local}, %% Store PLT in custom directory {plt_location, "custom_dir"}, %% Extra apps to include in the PLT {plt_extra_apps, [app1, app2]}, {warnings, [unmatched_returns, error_handling]} ]}.
* Add Dialyzer pluginTuncer Ayaz2015-05-221-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | Build project-specific PLT $ rebar build-plt Check the PLT for consistency and rebuild it if it is not up-to-date $ rebar check-plt Analyze the code for discrepancies $ rebar dialyze Delete project-specific PLT $ rebar delete-plt Valid rebar.config options: %% Store PLT in ~/.rebar/plt (Default) {dialyzer_plt_location,shared} %% Store PLT locally inside the project in .rebar {dialyzer_plt_location,local} %% Store PLT in custom directory {dialyzer_plt_location,"custom_path"} {dialyzer_plt_extra_apps,[app1,app2]} {dialyzer_warnings,[unmatched_returns,error_handling]}
* Fix rebar.config.sample formattingTuncer Ayaz2015-05-221-3/+3
|
* Merge branch 'dia_first_files' of https://github.com/fholzhauser/rebar into ↵Fred Hebert2015-05-091-0/+8
|\ | | | | | | fholzhauser-dia_first_files
| * Add option dia_first_files for the diameterfholzhauser2014-09-221-0/+8
| | | | | | | | | | With this option is is possible to provide a list of files to compile first. It is necessary when diameter dictionaries have dependencies.
* | Support custom protobuf directoryLuis Rascao2015-01-311-1/+6
| | | | | | | | | | | | | | | | | | | | | | proto_opts config option contains the compiler directive that defines which proto compiler to use, also contains a src_dirs entry that defines a list of locations for the .proto files to be processed. Add integration test that compiles .proto files from src and from proto directory specified in separate rebar config files
* | Add support for compiling proto files using gpbTomas Abrahamsson2014-10-291-0/+4
| | | | | | | | | | | | This adds the config option {proto_compiler,gpb} for selecting gpb as the compiler for protocol buffer files. When gpb is used as compiler, it reads the gpb_opts config item for options.
* | Introduce pluggable protocol buffer compilersTomas Abrahamsson2014-10-291-0/+6
|/ | | | | | | | | | | | | Make it possible for plug in alternative protocol buffer compilers. The compilers are picked up based on if they export all of the functions key/0, proto_compile/3, proto_clean/3 and proto_info/2. The set of compiler modules to choose from, is fetched from the rebar application environment, from the app_dir modules. A new config option, {proto_compiler,Compiler}, specifies which of the available protocol buffer compilers to use. The 'protobuffs' compiler is now one such compiler (the only one), and it is also the default, for backwards compatibility.
* Merge pull request #285 from nevar/fix_inheritanceTristan Sloughter2014-06-151-1/+1
|\ | | | | Fix #249 (erlc regression)
| * Fix #249 (erlc regression)Slava Yurin2014-05-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | The combination of changes to rebar_erlc_compiler, and the fact that erl_first_files is inherited, caused a regression. To fix that, ensure every project uses its own .rebar/erlcinfo. While at it, fix the issue that erl_first_files entries were not included when initializing the dep digraph. Reported-by: Louis-Philippe Gauthier Reported-by: Roland Karlsson Thanks: Tuncer Ayaz
* | Add 'p4' (Perforce) as a dependency typeNathaniel Waisbrot2014-03-171-2/+3
|/ | | | | | | 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
* Fix #56 (always-on recursion)Tuncer Ayaz2014-03-111-0/+3
| | | | | | | | | | | | | | | | | | Always-on recursive application of all rebar commands causes too many issues. Recursive application is required for: 1. dealing with dependencies: get-deps, update-deps, and compile of deps right after get-deps or update-deps 2. projects with a riak-like apps/ project structure and dev process The vast majority of projects are not structured like riak. Therefore, moving forward it's best to (by default) restrict recursive behavior to dealing with deps. This commit does that and also adds command line and rebar.config options for controlling or configuring recursion. Also, we introduce two meta commands: prepare-deps (equivalent to rebar -r get-deps compile) and refresh-deps (equivalent to rebar -r update-deps compile). riak-like projects can extend the list of recursive commands (to include 'eunit' and 'compile') by adding {recursive_cmds, [eunit, compile]} to rebar.config.
* introduce xref_extra_pathsmats cronqvist2014-01-131-0/+5
|
* Add missing dep examples and fix existing onesTuncer Ayaz2013-11-261-6/+19
|
* rebar_xref: regression fixes and updates for a5be40c96Tuncer Ayaz2013-06-241-1/+3
| | | | | | | | - restore support for "rebar help xref" - update rebar.config.sample - update 'help xref' string - simplify new/changed functions by breaking out code or using simpler syntax where applicable
* Update rebar repo urlsTuncer Ayaz2013-03-021-2/+2
|
* Implement 'rebar help CMD1 CMD2' and extend common 'rebar help' msgTuncer Ayaz2012-12-311-2/+2
| | | | | * allow plugins to print help message for implemented commands * append core rebar.config options to common 'rebar help' message
* rebar.config.sample: fix escript_emu_args sampleTuncer Ayaz2012-11-301-1/+1
|
* rebar.config.sample: remove non-existing optionTuncer Ayaz2012-11-201-5/+0
|
* rebar.config.sample: document escriptize optionsTuncer Ayaz2012-11-191-0/+7
|
* rebar.config: delete unused and unimplemented 'app_bin' optionTuncer Ayaz2012-11-191-3/+0
| | | | | app_bin option was used by the install command which has been removed in 51ed787.
* rebar.config.sample: document leex and yecc optionsTuncer Ayaz2012-11-181-0/+12
|
* rebar.config.sample: document require_*_vsn optionsTuncer Ayaz2012-11-181-0/+5
|
* rebar.config.sample: fix erl_opts exampleTuncer Ayaz2012-11-151-1/+3
|
* rebar.config.sample: fix raw dep example formattingTuncer Ayaz2012-11-151-10/+13
|
* rebar.config.sample: fix syntax errorTuncer Ayaz2012-11-141-1/+1
|
* Add support for non-Erlang/OTP (raw) dependenciesAnton Lavrik2012-10-111-1/+14
| | | | | | | | | | | | | | | | | | | | | | | | Introduce a new 'raw' option for dependency specs in rebar.config file. For example: {deps, {dependency_name, "1.0.*", {git, "<...>", {branch, "master"}}, [raw] } ]}. When this option is specified, rebar does not require the dependency to have a standard Erlang/OTP layout which assumes presence of either "src/dependency_name.app.src" or "ebin/dependency_name.app" files. 'raw' dependencies can still contain 'rebar.config' and even can have the proper OTP directory layout, but they won't be compiled. Only a subset of rebar commands will be executed on the 'raw' subdirectories: get-deps, update-deps, check-deps, list-deps and delete-deps.
* Document availability of rsync for fetching deps in rebar.config.sampleDaniel White2012-09-201-1/+2
|
* Separate eunit and qc compile optionsTuncer Ayaz2012-08-091-7/+14
|
* Add ct_log_dir option, skip test dir with no SUITEDeadZen2012-08-071-0/+3
| | | | | | | When rebar ct executes with its default common test directory of "test", it will generate a hardcoded "logs" directory in every application with a test directory present, causing an overlap with eunit's test framework so even test directories with only eunit tests will be processed by ct.
* Enable export of cover data from eunit testrunDavid Åberg2012-08-071-0/+3
|
* Rename old eunit compile options for consistency with test-compileTuncer Ayaz2012-07-261-6/+7
|
* Add 'qc' cmd and rename eunit-compile to test-compileTuncer Ayaz2012-07-231-0/+5
|
* Support ct_run using short nameTim Watson2012-05-221-0/+3
| | | | | | | | | | | Not every system under test can be run with long names, and this makes rebar's common_test support useless in those environments, as it currently uses long names (test@hostname.domain) by default, without recourse to change them. This patch adds support for a {ct_use_short_names, boolean()} config variable, which allows the user to specify whether short or long names are required.
* Remove alt_url support in favor of new featuresTuncer Ayaz2012-05-131-4/+1
|
* Add support for target-specific port optionsTuncer Ayaz2012-04-161-2/+4
| | | | {port_specs, [{".*", "priv/foo.so", ["c_src/foo.c"], [{env, []}]}]}.
* Fix whitespace errorTuncer Ayaz2012-04-151-2/+2
|
* Add support for custom xref queriesAmit Kapoor2012-04-021-0/+10
| | | | | | | | | | | | | | | | | | The custom queries are configured in rebar.config via the tuple {xref_queries, [{query(), query_result()},...]}. The implementation passes the query() string to xref:q and compares the return value with query_result(). It will result in an error if they do not match. The following configuration, for example, is the same as running the xref check undefined_function_calls. It additionally filters ejabberd_logger:*_msg/4 from the result as these functions are generated on execution by ejabberd and not available at compile time. {xref_queries, [{"(XC - UC) || (XU - X - B - (\"ejabberd_logger\":\".*_msg\"/\"4\"))",[]}]}. This patch also modifies the build process of this package by running a custom query instead of doing a diff against a static xref_warning file.
* Add support for alternate dependency urlsAdam Schepis2012-03-311-1/+4
| | | | | | This change adds the ability to use alternate urls for downloading dependencies. To make use of alternate urls run: rebar get-deps alt_urls=true
* Deprecate port_envs in favor of port_envTuncer Ayaz2012-03-091-1/+1
|
* Rework port compiler supportTuncer Ayaz2012-02-031-12/+6
| | | | | * consolidate options * add support for building executables
* Fix whitespace error in rebar.config.sampleTuncer Ayaz2012-01-291-1/+1
|
* Remove port_first_files supportTuncer Ayaz2012-01-091-3/+0
|
* Add support for customising common test directoryTim Watson2011-12-281-0/+3
| | | | | | | This patch allows users to specify the directory in which common_test source files can be found. Most common_test suites are integration, rather than unit tests and keeping the sources apart from test sources for other frameworks such as eunit and PropEr is a useful feature.
* Update sample hooks configTuncer Ayaz2011-12-051-1/+4
|
* Document port_first_filesTuncer Ayaz2011-11-301-0/+3
|
* Fix deps_dir sample configTuncer Ayaz2011-10-261-2/+2
|
* Load plugins dynamically from sourceTim Watson2011-08-291-0/+13
| | | | | | | | | This patch updates rebar_core to look for missing plugins (i.e. those that aren't found on the code path at runtime) in a configurable plugin directory, and dynamically compile and load them at runtime. By default, the directory "plugins" is searched, although this can be overriden by setting the plugin_dir in your rebar.config.
View Lorry Controller Status