summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #212 from tuncer/hrl-errorJared Morrow2014-01-161-19/+25
|\ | | | | Fix basho/rebar#388
| * rebar_base_compiler: replace fixed size list with a tupleTuncer Ayaz2014-01-151-4/+3
| |
| * Fix basho/rebar#388Tuncer Ayaz2014-01-151-16/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the syntax error is in a .hrl file, then the reported error message is not as useful because it's not clear which .erl file was being compiled. We can fix that easily by first printing what source file was being processed. We don't change the actual error message, so this will still work with your editor of choice for jumping to the right line. Before ------ Success: Compiled src/foo.erl Failure: include/foo.hrl:10: syntax error [...] After ----- Success: Compiled src/foo.erl Failure: Compiling src/foo.erl failed: include/foo.hrl:10: syntax error [...]
* | Merge pull request #215 from tuncer/experimentalJared Morrow2014-01-163-14/+3
|\ \ | | | | | | Remove experimental flags
| * | Remove experimental flagsTuncer Ayaz2014-01-143-14/+3
| | | | | | | | | | | | | | | | | | | | | | | | Remove experimental flag from: * qc compile_only=true * eunit compile_only=true * src/foo.app.src.script * eunit tests=
* | | Merge pull request #214 from tuncer/compile_onlyJared Morrow2014-01-162-2/+5
|\ \ \ | | | | | | | | Document compile_only=true
| * | | Document compile_only=trueTuncer Ayaz2014-01-142-2/+5
| |/ /
* | | Merge pull request #210 from tuncer/erlydtl-warningsJared Morrow2014-01-161-0/+4
|\ \ \ | |_|/ |/| | Fix #205 (erlydtl:compile/3 returns warnings)
| * | erlydtl: add missing clause (Reported-by: goofansu)Tuncer Ayaz2014-01-141-0/+2
| | | | | | | | | | | | erlydtl implemented 'binary' option. Add new clause for {binary, false}.
| * | Fix #205 (erlydtl:compile/3 returns warnings)Tuncer Ayaz2014-01-111-0/+2
| |/ | | | | | | | | Adapt rebar_erlydtl_compiler to handle warnings emitted by erlydtl:compile/3.
* | Merge pull request #191 from tuncer/rename-modulesJared Morrow2014-01-144-19/+93
|\ \ | | | | | | Fix #187 (rename getopt and mustache)
| * | Fix #187 (rename mustache to rebar_mustache)Tuncer Ayaz2014-01-012-5/+7
| | |
| * | Fix #187 (rename getopt to rebar_getopt)Tuncer Ayaz2014-01-012-14/+86
| |/ | | | | | | While at it, update getopt.erl to git rev 78eda3b.
* | Merge pull request #196 from tuncer/rebar-run-infoJared Morrow2014-01-141-1/+3
|\ \ | | | | | | Print a more appropriate message on 'rebar info'
| * | Print a more appropriate message on 'rebar info'Tuncer Ayaz2014-01-011-1/+3
| |/ | | | | | | | | | | | | To avoid treating plugins' info/2 functions as commands, we catch calls to 'rebar info'. Previously (4b8c81fb) we simply printed the help string, but it's much more informative to print the following: Command 'info' not understood or not applicable
* | Merge pull request #183 from EchoTeam/generate-upgrade-and-target-dirJared Morrow2014-01-141-5/+3
|\ \ | |/ |/| generate-upgrade can now take target_dir argument
| * generate-upgrade can now take target_dir argumentsnaky2013-12-031-5/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previous generate-upgrade required renames in rel/ directory: rebar generate ...changing code... mv rel/<release> rel/<release_prev> rebar generate rebar generate-upgrade previous_release=<release_prev> With the proposed changes you can now do the same without moving things: rebar generate # default target dir: rel/<release> ...changing code... rebar generate target_dir=<release_new> rebar generate-upgrade target_dir=<release_new> previous_release=<release>
* | Add command to rebar:command_names/0Pierre Fenoll2013-12-191-0/+1
| |
* | Add a library templatePierre Fenoll2013-12-192-0/+12
| |
* | rebar_dia_compiler: fix Dialyzer warningsTuncer Ayaz2013-12-171-2/+2
| |
* | Fix is_verbose/1 helper functionTuncer Ayaz2013-12-066-24/+30
| |
* | Write ERROR messages to standard_error deviceTuncer Ayaz2013-12-061-2/+6
| |
* | Change default log level to 'warn' and introduce -q/--quietTuncer Ayaz2013-12-062-12/+20
| |
* | rebar_log: use defines for log level numbersTuncer Ayaz2013-12-061-8/+12
| |
* | rebar_config:is_verbose/0: fix variable nameTuncer Ayaz2013-12-061-2/+2
| |
* | Make list of commands (for unabbreviation) easier to maintainTuncer Ayaz2013-12-041-5/+26
| | | | | | | | | | It's easier to modify the list with each command on a separate line. The shell completion scripts have already been modified that way.
* | Merge pull request #174 from tuncer/dialyzer-fixesJared Morrow2013-12-031-1/+1
|\ \ | | | | | | rebar_core: fix Dialyzer warning introduced in aa46d85 (#157)
| * | rebar_core: fix Dialyzer warning introduced in aa46d85 (#157)Tuncer Ayaz2013-11-261-1/+1
| | |
* | | Merge pull request #173 from tuncer/unknown-vsnJared Morrow2013-12-031-6/+8
|\ \ \ | | | | | | | | Fix false reporting of (plain) vsn strings
| * | | Fix false reporting of (plain) vsn stringsTuncer Ayaz2013-11-261-6/+8
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | rebar used to mistakenly report plain version strings like {vsn, "1.0.0"} as follows: DEBUG: vcs_vsn: Unknown VCS atom in vsn field: "1.0.0" Properly detect unknown/unsupported version terms and abort if we encounter one. While at it, rename a variable in vcs_vsn/3 to be non-misleading.
* | | Merge pull request #172 from tuncer/dep-examplesJared Morrow2013-12-031-11/+21
|\ \ \ | | | | | | | | Add missing dep examples and fix existing ones
| * | | deps: remove undocumented fossil syntaxTuncer Ayaz2013-11-261-4/+0
| | | | | | | | | | | | | | | | | | | | As discussed with Martin Schut, remove support for {app_name, "vsn", {fossil, "url", latest}.
| * | | Add missing dep examples and fix existing onesTuncer Ayaz2013-11-261-7/+21
| |/ /
* | | lfe: use correctly filtered erl_optsTuncer Ayaz2013-11-261-2/+2
| | |
* | | erlc: properly reuse the right erl_opts in test_compileTuncer Ayaz2013-11-261-3/+3
|/ / | | | | | | | | Avoid getting erl_opts twice in test_compile/3, and make sure the correctly filtered (platform_define, etc.) version is used.
* | Merge pull request #155 from tuncer/fixesJared Morrow2013-11-263-70/+84
|\ \ | |/ |/| Fixes for #137 and #142
| * Fix issues introduced in #137 (4dfdd72)Manuel Rubio2013-10-161-13/+14
| | | | | | | | | | * fix Dialyzer warning * fix formatting
| * rebar_deps: fix overly long linesTuncer Ayaz2013-10-161-39/+50
| |
| * rebar_deps: 'depowner' has to be stored in xconfTuncer Ayaz2013-10-161-7/+9
| |
| * rebar_deps: fix Dialyzer warningTuncer Ayaz2013-10-161-9/+9
| |
| * 'current_command' has to be stored in xconfTuncer Ayaz2013-10-162-2/+2
| |
* | Merge pull request #157 from Vagabond/adt-lib-dirJared Morrow2013-11-221-4/+5
|\ \ | | | | | | Don't over-aggressively clean the code path in the presence of lib_dir directives
| * | Don't badmatch if a path we think we added isn't in the code pathAndrew Thompson2013-10-171-1/+1
| | |
| * | Don't over-aggressively clean the code path in the presence of lib_dir ↵Andrew Thompson2013-10-161-4/+5
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | directives Rebar, when it encounters a lib_dir directive, caches the current code path, adds the libdir(s) and returns the cached copy of the path. When rebar has finished processing that directory, it restores the cached path. This is problematic in the below scenario: /(lib_dir)->G A -> B -> C -> D -> E \-> F -> D -> E When rebar is finished processing B, it restores the code path to what it was before it processed B, removing C, D, E and G from the code path. This means when it comes to process F, neither D or E are in the code path, so any header includes, rebar plugins or parse transforms will not be in the code path. Without the lib_dir directive, rebar does no code path cleanups, so everything works fine. This change makes rebar only remove the explicit lib_dir code paths it added and adds an inttest that replicates the above scenario.
* | Fix update-deps with certain forms of the {tag, ...} typeAndrew Thompson2013-10-161-1/+1
|/ | | | | | | Sometimes tags like 1.1-3-g3af5478 or d20b53f0 are encountered. The first is the output of 'git describe', and the second is just a regular git SHA. git fetch --tags will not pull these down, so do a full git fetch instead.
* Merge pull request #142 from Vagabond/adt-update-depsDave Smith2013-10-142-37/+141
|\ | | | | Make update-deps traverse deps breadth-first, top-down
| * Address review comments and add inttest for update-depsAndrew Thompson2013-09-302-3/+3
| |
| * Fix skip check for deps not presentAndrew Thompson2013-09-241-6/+10
| |
| * Make update-deps honor apps= and skip_apps=Andrew Thompson2013-09-232-1/+21
| | | | | | | | | | | | | | | | | | | | | | | | Because rebar_core handles skipping apps, we had to specialcase the handling in the case of update-deps because it has to do its own dep handling. The way this was done is not particularly clean, but there currently does not exist another way for a command to signal rebar_core that it doesn't want rebar_core to pay attention to skip_apps. With this change, however, you can update-deps even with local conflicting changes/commits by simply skipping the deps you don't wish to update, or whitelisting he ones you do wish to update.
| * Change how update-deps updates a git branchAndrew Thompson2013-09-231-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, update-deps on a dep tagged as {branch, ...} would do the following: git fetch git checkout -q origin/<branch> If you were already on that branch, the repo would end up in detached head state. This is kind of annoying if you're doing local development. This patch changes the behaviour to be git fetch git checkout -q <branch> git pull --ff-only --no-rebase -q <branch> The intent of this is to move the branch's HEAD forward to match upstream without destroying any local commits or changes, and without accidentally causing merges or rebases. It will fail if the operation can not be performed without losing history, merging or rebasing. The previous behaviour has been around a very long time: https://github.com/rebar/rebar/commit/064195dc5a90f5b0cc3ae92e8373671b0043033f#L0R308 It also exactly mirrors the download_source case, which is not really true. With git tags and SHAs, one can assume that they don't change, but branches move all the time.
generated by cgit v1.1 at 2024-12-28 15:01:52 +0000