| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
The DirRef in the spec file is relative to the directory where the spec
file is located. ct2_rt was erroneously copying the spec file to test/.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Avoid overwriting custom config (passed with -C) when we are processing
the base_dir in rebar_core.
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
Currently the --config switch does not work because when loading
a new rebar config the global setting is ignored for all paths.
This patch provides a check when loading new rebar config to see
whether or not the current config path matches the `base_dir` set in
global conf, which produces the expected behaviour.
|
|
|
|
|
|
|
|
|
| |
This change makes it possible to assign pre/post scripts to all
rebar commands. This allows users fine grained control over
when scripts and/or shell commands should be executed, where such
extensions are absolutely needed.
Several examples have been added to the rebar.config.sample file.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change adds support for executing ct test runs based on test
specificiations, which was missing previously. The rebar_ct module
now looks for any number of files with a name ending in `test.spec`
and if it finds one or more, passes these after the `-spec` argument
to ct_run instead of explicitly configuring the config, user config
and coverage config variables.
When no specifications are found, then the module behaves as it did
before this change, and both the ct1 and (new) ct2 integration tests
appear to show this is a backwards compatible patch.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
--HG--
extra : rebase_source : 5035f025b5873cedfb67e42159c5ce95b07c198d
|
|
|
|
|
| |
--HG--
extra : rebase_source : cd143fdf55773dcfbeeda687570b226def42e4f5
|
|
|
|
|
| |
--HG--
extra : rebase_source : c0bfcfbbbca005eee2a3434cbe25494399b07532
|
|
|
|
|
| |
--HG--
extra : rebase_source : 1998dc102f89c3c809d5146c800218b5c5b6cba9
|
|
|
|
|
|
|
| |
tdeps1_rt to use it
--HG--
extra : rebase_source : 010907d47b360288825cb9c841d62450700be225
|
| |
|
| |
|
|
|