summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Add module directory to include pathLuis Rascao2016-01-261-2/+3
| | | | | | | | | | Several projects use an include path relative to the project's root. file:compile will look in three places for the include files: The current working directory The directory where the module is being compiled The directories given by the include option
* Merge pull request #1031 from tsloughter/masterFred Hebert2016-01-241-11/+15
|\ | | | | add profile option to clean task
| * add profile option to clean taskTristan Sloughter2016-01-231-11/+15
| |
* | Merge pull request #1024 from talentdeficit/dedupe_eunit_default_testsTristan Sloughter2016-01-231-10/+39
|\ \ | |/ |/| deduplicate default test set generated by `rebar3 eunit`
| * deduplicate default test set generated by `rebar3 eunit`alisdair sullivan2016-01-171-10/+39
| | | | | | | | | | this ONLY attempts to deduplicate test sets that are generated by rebar in the absence of any user specified tests
* | move unstable install and upgrade to local namespaceTristan Sloughter2016-01-222-2/+2
| |
* | add support for setting erl vm args with REBAR3_ERL_ARGSTristan Sloughter2016-01-221-1/+1
| |
* | Display error message when bad config is loadedFred Hebert2016-01-171-2/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If a bad configuration file is submitted to rebar3 shell, display the following error: ===> The configuration file submitted could not be read and will be ignored. And keep going otherwise rather than silently failing. While crash-fast is usually a good mechanism, the shell so far is very tolerant of failures from apps to boot and whatnot, so this feels appropriate. Fixes #1019
* | Merge pull request #1017 from talentdeficit/runtime_version_checkFred Hebert2016-01-171-5/+8
|\ \ | |/ |/| check at runtime instead of compile time for `file:list_dir_all/1`
| * check at runtime instead of compile time for presence of `file:list_dir_all/1`alisdair sullivan2016-01-131-5/+8
| | | | | | | | | | | | this is slower than the compile time check but i guess packaging rebars with repos is still a thing and i think only the eunit and ct providers call it anyways
* | Merge pull request #1018 from talentdeficit/cover_what_are_you_doooooingFred Hebert2016-01-161-4/+3
|\ \ | | | | | | change detection of valid modules for `eunit`
| * | change detection of valid modules for `eunit`alisdair sullivan2016-01-131-4/+3
| |/ | | | | | | | | | | | | `beam_lib:chunks(..)` needs a path to object code which, frustratingly, `code:which/1` won't return for cover compiled modules. instead just assume that if `code:which/1` doesn't return `non_existing` a module is something we can run tests on
* | Merge pull request #1021 from tsloughter/masterTristan Sloughter2016-01-151-1/+2
|\ \ | |/ |/| convert 'app' to 'application' in eunit_opts to match cmdline args
| * convert 'app' to 'application' in eunit_opts to match cmdline argsTristan Sloughter2016-01-151-1/+2
| |
* | when using the `--file' argument to `eunit' paths were being convertedalisdair sullivan2016-01-121-9/+20
|/ | | | into directory test arguments
* Merge pull request #995 from ferd/fix-old-shellTristan Sloughter2016-01-102-3/+790
|\ | | | | Support old-style shell for rebar3 shell
| * Correct TTY type detectionFred Hebert2016-01-061-17/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This reuses the trick used within OTP to pick within old and new shell. The 'user' structure is the same for all cases (escript, escript + dumb TERM, unstable install, unstable install + dumb TERM), so we take it down first. Then we boot the TTY driver, which fails if TERM=dumb, in which case we boot the retro-style usr. If it worked, we shut down the driver again, and boot a modern shell structure. This avoids all warnings and seems to work in all cases.
| * Support old-style shell for rebar3 shellFred Hebert2016-01-062-0/+781
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is quite the hack. This requires to detect the current shell running; if it's the new shell, business as usual. However, if it's the old shell, we have to find a way to take over it and drive IO. This requires a few steps because: - the old shell does not let you be supervised intelligently (it uses supervisor_bridge, so killing the child is not a supported operation from the supervisor) - the old shell ignores all trappable exit signals except those coming from the Port in charge of stdio ({fd, 0, 1}) - the old shell shuts down on all exit signals from the stdio Port except for badsig, and replicates the shutdown reason otherwise - An escript does not tolerate the `user` process dying (old shell) for any non-normal reason without also taking the whole escript down - Booting in an escript has an implicit 'noshell' argument interpreted by the old shell as a way to boot the stdio Port with only stdout taken care of Because of all these points, we have to kill the old `user` process by sending it a message pretending to be the Stdio port dying of reason `normal`, which lets it die without triggering the ire of its supervision tree and keeping the escript alive. This, in turn, kills the old stdio port since its parent (user.erl) has died. Then we have to boot our copy of user.erl (rebar_user.erl) which conveniently ignores the possibility of running the stdio port on stdout only -- always using stdin *and* stdout, giving us a bona fide old-style shell. A known issue introduced is that running r3:do(ct) seems to then kill the shell, and r3:do(dialyzer) appears to have an odd failure, but otherwise most other commands appear to work fine.
* | Merge pull request #1009 from tsloughter/masterFred Hebert2016-01-101-1/+11
|\ \ | | | | | | merge overlay entries into a single {overlay, list()} for relx
| * | merge overlay entries into a single {overlay, list()} for relxTristan Sloughter2016-01-101-1/+11
| | |
* | | Unquote templates, add a warning instead.Fred Hebert2016-01-101-0/+25
|/ /
* | install project app plugins after discovering them not beforeTristan Sloughter2016-01-103-4/+13
| |
* | Merge pull request #1006 from tsloughter/masterFred Hebert2016-01-092-4/+5
|\ \ | | | | | | only apply default and prod profile to dependencies
| * | only apply default and prod profile to dependenciesTristan Sloughter2016-01-092-4/+5
| | |
* | | Merge pull request #999 from ferd/fix-windows-stuffTristan Sloughter2016-01-081-4/+12
|\ \ \ | |/ / |/| | Fix windows stuff
| * | fix dirs robocopy and canonical paths in windowsFred Hebert2016-01-071-4/+12
| |/ | | | | | | | | | | | | | | | | | | | | | | - robocopying a directory into another directory recursively expects the directory name to be properly mapped onto the destination, otherwise all the files are copied into the given path. This patches things so a directory-to-directory robocopy works as expected in a linux mindset so tests pass - the test for canonical paths didn't expect a windows environment at all; the test (and library) is modified to be consistent in that environment: always with a native format and with proper support of drive letters.
* | only need to compare ref and not ref+url in git resourceTristan Sloughter2016-01-081-2/+2
| |
* | warn if the directories `eunit' or `ct' show up in `src_dirs'alisdair sullivan2016-01-051-2/+17
|/ | | | | | | | if these directories actually exist they'll be added to the path ahead of the release/standard distribution directories and they'll break eunit and/or ct execution fixes #950
* Merge pull request #966 from talentdeficit/ct_root_suitesFred Hebert2016-01-052-3/+33
|\ | | | | allow ct suites to be specified at root of project (or root of app)
| * put `extra' ct test suites in `extras/apps/APPNAME' rather than `extras'alisdair sullivan2015-12-201-1/+2
| | | | | | | | this allows repeated test suite names across apps without conflicts
| * allow ct suites to be specified at the root of a project (or root of app)alisdair sullivan2015-12-202-2/+31
| | | | | | | | | | | | | | | | previously rebar3 dropped suites declared at the root of the project (via `--suite=whatever_SUITE' probably) and warned. this was because the compiler would recursively copy and compile everything in the directory indicated by the test suite. this changes the copy mechanism to only copy erl source files and directories that end with `_SUITE_data' into the `extras' dir in `_build'
| * whitespace cleanupalisdair sullivan2015-12-201-1/+1
| |
* | convert ~> versions to highest matchingTristan Sloughter2015-12-261-24/+14
| |
* | Merge pull request #987 from ferd/plugin-templatesTristan Sloughter2015-12-213-7/+35
|\ \ | |/ |/| Plugin templates
| * Plugin templates enabledFred Hebert2015-12-193-7/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This lets a plugin define templates to be loaded: $ rebar3 new ... proper (plugin): A basic PropEr suite for an OTP application ... $ rebar3 new help proper proper: plugin template (...) Description: A basic PropEr suite for an OTP application Variables: name="suite" (...) ... → rebar3 new proper fakesuite ===> Writing test/prop_fakesuite.erl In this case, proper is a fake template file I've put by hand in _build/default/plugins/rebar3_proper/priv/<somename>/, meaning it will only work as far as it's called from the project's root. The priority order of plugins is now .config > plugin > built-in, such that someone could ensure plugins do not crush their own private templates, but also that custom or plugin templates do overtake built-in ones. It used to be Built-in > .config only. Templates are searched for recursively in the priv/ directory of plugins.
* | support temporary cdn change with HEX_CDN os varTristan Sloughter2015-12-196-46/+89
|/
* Merge pull request #988 from ferd/schutm-wrong-pathsTristan Sloughter2015-12-191-1/+30
|\ | | | | Fix wrong relative path resolution
| * Merge branch 'master' of https://github.com/schutm/rebar3 into ↵Fred Hebert2015-12-191-1/+30
| |\ | | | | | | | | | schutm-wrong-paths
| | * Fix wrong relative path resolutionschutm2015-12-101-1/+30
| | |
* | | Merge pull request #986 from ferd/fix-bad-tpl-index-handlingTristan Sloughter2015-12-192-10/+28
|\ \ \ | |/ / |/| | A bad template index does not crash; shows warning
| * | A bad template index does not crash; shows warningFred Hebert2015-12-182-10/+28
| |/ | | | | | | | | | | | | | | This should fix #955 The test is implicit as a bad index previously silently crashed rebar3. By adding the bad index to the `new` suite's files, we can show that things keep running.
* | Account for division by zeroPanagiotis PJ Papadomitsos2015-12-161-0/+2
| |
* | Add support for total code coveragePanagiotis PJ Papadomitsos2015-12-161-0/+16
|/
* Merge pull request #967 from talentdeficit/mib_include_fixFred Hebert2015-12-081-31/+33
|\ | | | | symlink mib hrl output in apps `include' directories
| * remove mib header file in `priv/mibs/include'alisdair sullivan2015-12-081-7/+1
| |
| * symlink mib hrl output in apps `include' directoriesalisdair sullivan2015-12-061-31/+39
| | | | | | | | this restores compatibility with rebar2 and erlang.mk
* | Actually fix tuple merging.Fred Hebert2015-12-061-30/+53
|/ | | | Full rewrite, code should be understandable now.
* Fix tuple umergingFred Hebert2015-12-061-7/+18
| | | | | | | | | | | | - proper segregation of comparison between tuple terms and non-tuple terms. Guards weren't specific enough and that meant the wrong clauses of guards would be triggered - proper deduplication of entries in the list. An additional N passes are required (we co-opt the reverse step to be more efficient) because while the original lists:umerge easily removes dupes, this is requiring more logic here since `[a,{a,b},{a,b,c},a,{a,b,c}]` is a possible interleaving and we'd want `[a,{a,b},{a,b,c}]` -- comparison of direct neighbours isn't enough.
* Merge pull request #948 from toland/fix_mib_compilerFred Hebert2015-12-011-4/+8
|\ | | | | Fix a small bug in the MIB compiler when building dependencies
| * Added tests and fixed a bugPhil Toland2015-12-011-1/+1
| |
generated by cgit v1.1 at 2024-12-27 06:38:55 +0000