summaryrefslogtreecommitdiff
path: root/rebar.config
Commit message (Collapse)AuthorAgeFilesLines
* Reload logger config in CT suitesFred Hebert2019-10-041-1/+1
| | | | | | | | | | | | | | | | | | | Fixes #2159; this is done by force-reloading the handlers to match the config. This can create a bit of a funny effect if sys.config specifies an INFO log level (or lower) is specified. While apps are booted for config changes before the cth_failonly hook is enabled, supervision and other application log messages can start being output. They will start being suppressed once the CT run begins. This is not a bug, it's a race in instantiation of control and enabling of log levels. Nothing we can do about that. It might however surprise people a good bit. If non-default stdout handlers are added, they are similarly likely to become noisy; specifying a test-specific sys.config file may be necessary then. Also includes a bump of cth_readable version, which now checks for updates to the log formatter on every test output.
* upgrade relx 3.33.0Tristan Sloughter2019-08-201-1/+1
|
* Repair edoc functionality on rebar3 itselfFred Hebert2019-07-251-0/+2
|
* Bump cth_readable to fix lager on OTP-21+Fred Hebert2019-07-041-1/+1
|
* bump relx to 3.32.1 and providers to 1.8.1Tristan Sloughter2019-06-011-2/+2
|
* upgrade ssl_veirfy_fun to 1.1.5Tristan Sloughter2019-05-301-1/+1
|
* upgrade relx to 3.32.0Tristan Sloughter2019-05-271-1/+1
|
* Remove pre-17 namespaced types workaroundFred Hebert2019-05-141-2/+1
|
* Make test suite pass on OTP-22Fred Hebert2019-05-141-1/+1
| | | | | - fix some bad typespec - bump the meck version for good fortune
* Fix cth_readable crash with bad lager interactionFred Hebert2019-05-041-1/+1
| | | | fixed #2063
* upgrade relx 3.31.0Tristan Sloughter2019-04-141-1/+1
|
* Update certifi, ssl_verify_fun, bbmustacheFred Hebert2019-04-131-3/+3
|
* upgrad relx to 3.30.0Tristan Sloughter2019-04-121-1/+1
|
* upgrade relx 3.29.0Tristan Sloughter2019-03-131-1/+1
|
* Fix fetching of private packages from orgs on hex repos (#2020)Bryan Paxton2019-03-071-1/+0
| | | | | | | | | | | | | - vendor in hex_core at v0.5.0 - Change where repo_name should be the org and not the parent - Changed rebar_utils:url_append_path/2 to not explicitly add a '?', this is returned in the Query chunk by http_uri:parse/1 (e.g., "?foo=bar") - update organization_merging test to expect the sub-repo as the repo_name - Add tests for rebar_utils:url_append_path/2 - Stop referencing/setting "organization" in config and use new organization settings (api_repository and repo_organization) - Do not set (assume) the read key is valid for any/every repo - Set repo_organization and api_repository to org - Update tests to check for new config opts
* Bump cth_readableFred Hebert2019-02-051-1/+1
| | | | | Handles some internal changes in logger in OTP-21.2 that broke the follow-up error printouts after the first failure of a CT run
* update relx to 3.28.0Tristan Sloughter2019-01-051-1/+1
|
* Update hex_core and add mirror_of repo configEric Meadows-Jönsson2018-12-301-1/+1
|
* bump erlware_commons to 1.3.1Tristan Sloughter2018-12-181-1/+1
|
* fix to include beams built from src files in subdirs in modules listTristan Sloughter2018-11-231-1/+1
|
* fix finding transitive deps with prerelease versions (#1914)Tristan Sloughter2018-10-141-1/+1
|
* Bump bbmustache and fix templates (#1862)Fred Hebert2018-10-051-1/+1
| | | | | | | | | * bump bbmustache to version 1.6.0 * Use alternative bbmustache brackets in templates This fixes the problems where literal nested tuples (`{{a,b},c}` or `{{a,b}}`) would blow up and spaces needed to be inserted.
* compiler behaviour (#1893)Tristan Sloughter2018-10-051-0/+1
| | | | | | | | | | | | | | | | * add compile type for dynamic project compilation * new rebar_compiler abstraction for running multiple compilers rebar_compiler is a new behaviour that a plugin can implement to be called on any ues of the compile provider to compile source files and keep track of their dependencies. * fix check that modules in .app modules list are from src_dirs * use project_type to find module for building projects * allow plugins to add project builders and compilers
* upgrade relx and set base_dir in overlay_vars (#1902)Tristan Sloughter2018-10-051-1/+1
|
* properly support top level app erl_opts from REBAR_CONFIG os var (#1889)Tristan Sloughter2018-09-211-1/+2
| | | | | | When REBAR_CONFIG was set it would not effect the top level app's configuration because app_discover was rereading the top level rebar.config which ignored REBAR_CONFIG. Instead this patch has it use the existing configuration from REBAR_CONFIG.
* support for hex v2, multiple repository fetching, private organizations (#1884)Tristan Sloughter2018-09-131-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * update to hex_core for hex-v2 repo support (#1865) * update to hex_core for hex-v2 repo support This patch adds only single repo hex-v2 support through hex_core. Packages no longer filtered out by buildtool metadata and the package index is updated per-package instead of fetched as one large ets dump. * tell travis to also build hex_core branch * support list of repos for hex packages (#1866) * support list of repos for hex packages repos are defined under the hex key in rebar configs. They can be defined at the top level of a project or globally, but not in profiles and the repos configured in dependencies are also ignored. Searching for packages involves first checking for a match in the local repo index cache, in the order repos are defined. If not found each repo is checked through the hex api for any known versions of the package and the first repo with a version that fits the constraint is used. * add {repos, replace, []} for overriding the global & default repos * add hex auth handling for repos (#1874) auth token are kept in a hex.config file that is modified by the rebar3 hex plugin. Repo names that have a : separating a parent and child are considered organizations. The parent repo's auth will be included with the child. So an organization named hexpm:rebar3_test will include any hexpm auth tokens found in the rebar3_test organization's configuration. * move packages to top level of of hexpm cache dir (#1876) * move packages to top level of of hexpm cache dir * append organization name to parent's repo_url when parsing repos * only eval config scripts and apply overrides once per app (#1879) * only eval config scripts and apply overrides once per app * move new resource behaviour to rebar_resource_v2 and keep v1 * cleanup use of rebar_resource module and unused functions * cleanup error messages and unused code * when discovering apps support mix packages as unbuilt apps (#1882) * use hex_core tarball unpacking support in pkg resource (#1883) * use hex_core tarball unpacking support in pkg resource * ignore etag if package doesn't exist and delete if checksum fails * add back tests for bad package checksums * improve bad registry checksum error message
* Bump certifiFred Hebert2018-08-021-1/+2
| | | | Includes an update to parse_trans on an OTP-21 friendly version
* bump erlware_commons and relx for eperm otp-21 fixTristan Sloughter2018-06-231-2/+2
|
* Bump cth_readable for OTP-21 compatFred Hebert2018-06-191-1/+1
|
* Revert "upgrade certifi to 2.3.1"Tristan Sloughter2018-06-191-2/+1
|
* upgrade relx to 3.25.0Tristan Sloughter2018-06-191-1/+1
|
* upgrade certifi to 2.3.1Tristan Sloughter2018-06-121-1/+2
|
* upgrade bbmustache to 1.5.0Tristan Sloughter2018-06-121-1/+1
|
* Logger OTP-21-rc2 supportFred Hebert2018-05-301-1/+1
| | | | Also small output fix in rebar3 shell
* Restore default templates in bootstrapped rebar3Fred Hebert2018-05-091-0/+4
| | | | | | | | | | | | | | When allowing Dialyzer to work internally, we moved a bunch of config (such as no_debug_info) to the prod profile, but the escript included files remained locked onto the default profile. Because the bootstrapping phase now happened in a prod run, the priv/ dirs were never created for the default profile unless a prior run existed, which hid the bug from us. This patch overrides the path on the prod profile so that we don't rely on accidental leftovers for things to work on a bootstrap phase as a dev.
* start at least one async thread in async thread poolGrigory Starinkin2018-05-081-2/+1
| | | | | fixes an issue when shell is terminated with an error "Bus error: 10", on attempt to run rebar shell with verbose logging
* Logger support in cth_readable; compact CT outputFred Hebert2018-05-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | cth_readable 1.4.0 supports the new logger interface from OTP-21, which likely breaks compatibility with R16 builds. It also includes a new compact interface, displaying output such as: ===> Running Common Test suites... %%% rebar_alias_SUITE: ...... %%% rebar_as_SUITE: ........... %%% rebar_compile_SUITE:................................ ............................ %%% rebar_compile_SUITE ==> test_name: SKIPPED %%% rebar_compile_SUITE ==> {tc_user_skip,"compile:env_compiler_options/0 available"} .. %%% rebar_cover_SUITE: ............. %%% rebar_ct_SUITE: .................................... Allowing to display more tests within less screen space. This mode has been added to the ct_readable option under the name 'compact' (now supporting true | false | compact), and has been made default for rebar3.
* Re-disable debug_info on prod profileFred Hebert2018-05-031-0/+1
| | | | Had mistakenly only disabled it for deps.
* Work around OTP-21 deprecation of get_stacktrace()Fred Hebert2018-05-031-0/+2
| | | | Based off a macro by @okeuday at https://github.com/erlang/otp/pull/1783
* Update erlware_commons for stacktraces supportFred Hebert2018-05-031-1/+1
|
* Bump cth_readable to 1.3.4: restor eunit formatFred Hebert2018-04-221-1/+1
|
* Fix various Dialyzer warningsFred Hebert2018-04-201-1/+4
| | | | | | | | | Some still remain from erl_type calls from Dialyzer, but most of them are handled. Decided to just ignore rebar_alias since playing with the type specs of abstract code format is just a nightmare and hard to do cross-versions I guess.
* Make rebar3 work with dialyzer internallyFred Hebert2018-04-141-31/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We got funny interactions since PR #1656: - the last `debug_info`-related option seen in a list of options after profile merge is kept, allowing later profiles from overtaking earlier ones - if you go `rebar3 as a,b,c compile`, the options from profile A come before B, which come before C, so C's options win - overrides are applied in order of profile as well, giving a priority to a later profile than an earlier one - The values in overrides are prepended rather than suffixed to the existing list - this means if we have to overrides adding options, such as `default` adding `no_debug_info', and `dialyze` adding `debug_info`, the results are `[debug_info]` as `dialyze` is applied first, and then `[no_debug_info, debug_info]` as `default` overrides are applied - the final result is `no_debug_info` always winning when erl_opts are overriden specifically. only `debug_info` options are going to suffer this, and in the context of overrides. Other `erl_opts` should be fine. I'm not sure how that can be fixed at all. In the meanwhile, we can add support back while leaving the default to not having debug information. This is done by: - moving all `no_debug_info` options to the `prod` profile - forcing `prod` to be called by `./bootstrap` so that most people keep getting no debug info - anyone calling `rebar3 clean -a` and then rebuilding with `rebar3 escriptize` (i.e. rebar3 devs) get debug info going This is up for review and discussion.
* Bump cth_readable to 1.3.3Fred Hebert2018-04-031-1/+1
| | | | Fixes some lager warnings since config changes
* upgrade erlware commons and relxTristan Sloughter2018-02-031-2/+2
|
* Fix Plugin path handling (again!)Fred Hebert2017-12-041-0/+4
| | | | | | | | | | | | | | | | | | | The path reloading of plugins had been fixed properly, but the problem is that the paths it was using to re-load only considered the current compile step, rather than the overall state of plugins. As such, the reloaded paths after plugin compilation only reloaded the *latest* plugin and not the other ones. This fix forces the addition of all built plugin paths to the code paths after a plugin compile job is run. This ensures that the path is clean for initial plugin deps (only add those that are required), and is re-made total after the fact (add all the plugins possible). This commit also includes a system tests suite that can be run optionally; the problem with this plugin mechanism was impossible to find through mocked dependencies, and a working counterexample was provided to us. The systest suite can be run against real projects without conflict to make sure no regressions are hit.
* Merge pull request #1665 from ferd/bump-cth_readable-1.3.2Fred Hebert2017-11-221-1/+1
|\ | | | | Bump cth_readable to 1.3.2
| * Bump cth_readable to 1.3.2Fred Hebert2017-11-201-1/+1
| | | | | | | | Eliminates a lager warning due to config format deprecation
* | upgrade relx to 3.24.3Tristan Sloughter2017-11-211-1/+1
|/
* upgrade relx and erlware commonsTristan Sloughter2017-11-171-2/+2
|
generated by cgit v1.1 at 2024-12-26 07:11:25 +0000