summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Add fail_on_warning support for LFETim Dysinger2011-02-211-4/+8
|
* Add -spec support to rebar_ct command lineTim Watson2011-02-211-21/+49
| | | | | | | | | | | | | 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.
* Clean up and simplify {vsn, VCS} supportDave Smith2011-02-181-12/+11
|
* Add {vsn,Vcs} support for bzr, hg and svnTuncer Ayaz2011-02-171-6/+15
|
* Expand {vsn,git} in app.src to git-describe outputAdam Kocoloski2011-02-172-2/+14
|
* Clean up trailing whitespacejoewilliams2011-02-173-5/+5
|
* Clean up rebar_appups and rebar_upgradejoewilliams2011-02-174-109/+92
|
* Add PropEr supportTuncer Ayaz2011-02-161-17/+24
|
* Fix generate-appups regression (atom vs list)joewilliams2011-02-161-1/+1
|
* Add 'generate-appups' commandjoewilliams2011-02-153-3/+230
| | | | | | | | | | | | | | | To further support OTP releases I have added support for generating application appup files. These include instructions that systools uses to generate a relup file which contains the low level instructions needed to perform a hot code upgrade. My goal with this module is to produce "good enough" appup files or at least a skeleton to help one get started with something more complex. If an appup file already exists for an application this command will not attempt to create a new one. Usage: $ rebar generate-appups previous_release=/path/to/old/version Generally this command will be run just before 'generate-upgrade'.
* Give an absolute path to code:add_path/1Anthony Ramine2011-02-151-1/+1
| | | | | | | If an app uses -include_lib for its own included files, compilation fails if the app directory isn't in $ERL_LIBS because code:lib_dir/1 will return an error. An absolute path needs to be added to code path instead of just "ebin".
* Remove export_all directiveTuncer Ayaz2011-02-131-3/+2
|
* Add eunit_first_files optionJoseph Wayne Norton2011-02-131-1/+4
|
* Support 2 forms of implicit HEAD for gitDavid Reid2011-02-131-0/+8
| | | | | | | | In git origin/HEAD is a pointer to the default branch. This patch allows two alternatives to explicitly specifying "HEAD" in git VC specs. The first is a 2 arity form {git, Url} and the second is {git, Url, ""} which worked in pre-update-deps rebars.
* Clean up codeTuncer Ayaz2011-02-0626-385/+523
|
* Clean up emacs file local variablesTuncer Ayaz2011-01-3133-33/+33
|
* Fix Dialyzer warnings in rebar_upgradeTuncer Ayaz2011-01-291-2/+2
|
* Move BUILD_TIME and VCS_INFO macrosTim Watson2011-01-292-8/+8
| | | | | | I have moved these macros from rebar_core.erl to rebar.erl in order to prevent eunit tests from failing (which they currently are).
* Use filename:join instead of ?FMTTuncer Ayaz2011-01-281-2/+4
|
* Fix help: previous_release is mandatoryTuncer Ayaz2011-01-281-1/+1
|
* Add 'generate-upgrade' commandjoewilliams2011-01-272-2/+210
| | | | | | | | | | | | | | | | | | | | | To support OTP release upgrades I have added support for building upgrade packages. Support for this is included in the rebar_upgrade module, specifically generate_upgrade/2. It requires one variable to be set on the command line 'previous_release' which is the absolute path or relative path from 'rel/' to the previous release one is upgrading from. Running an upgrade will create the needed files, including a relup and result in a tarball containing the upgrade being written to 'rel/'. When done it cleans up the temporary files systools created. Usage: $ rebar generate-upgrade previous_release=/path/to/old/version This also includes a dummy application that can be used to test upgrades as well as an example. Special thanks to Daniel Reverri, Jesper Louis Andersen and Richard Jones for comments and patches.
* Fix circular dependencyTuncer Ayaz2011-01-272-45/+45
|
* Use an order independent method for exact matches when looking for command ↵Dave Smith2011-01-251-3/+3
| | | | candidates
* Add support for abbreviated command namesKlas Johansson2011-01-242-12/+75
| | | | | | | | | | | | | | | | | | | This change makes it possible to type the beginning (the prefix) of a command name and rebar will guess the full name of the command, thereby saving the user precious keystrokes. As long as the prefix matches only one command, rebar runs that command, otherwise rebar prints a list of candidate command names. The "-" character is considered to be a word separator and the prefix matching is done per word. Example prefix matches: co ==> compile cl ==> clean create ==> create create-a ==> create-app c-a ==> create-app c-app ==> create-app
* Move command line handling funs into rebar.erlTuncer Ayaz2011-01-242-173/+187
|
* Update getoptTuncer Ayaz2011-01-231-6/+13
|
* Add support for arch specific port_sourcesAndrew Tunnell-Jones2011-01-171-1/+13
| | | | | | | | | On one project I have a need to specify port_sources on R14 only and on another different project port_sources for Darwin and Linux. To this end add support to handle tuples of the form {ArchRegex, PortSource} in the port_sources list, eg: {port_sources, [{"R14", ["c_src/*.c"]}]}.
* Fix underspec (thanks Kostis Sagonas)Tuncer Ayaz2011-01-131-1/+1
|
* Simplify rebar_coreTuncer Ayaz2011-01-131-23/+17
|
* Fix grep invocationsTuncer Ayaz2011-01-132-13/+23
|
* Fix indentation in rebar_ctTuncer Ayaz2011-01-131-20/+20
|
* Simplify and cleanup rebar_templaterTuncer Ayaz2011-01-131-10/+11
|
* Simplify and cleanup rebar_xrefTuncer Ayaz2011-01-131-21/+9
|
* Apply Tidier suggestionsTuncer Ayaz2011-01-1311-70/+77
|
* Fix typosTuncer Ayaz2011-01-132-3/+3
|
* Fix file existence checksTuncer Ayaz2011-01-135-5/+5
|
* Fix code clarityTuncer Ayaz2011-01-133-20/+24
|
* Add otp_release to platform stringJoseph Wayne Norton2011-01-092-7/+21
|
* Fix Dialyzer warningTuncer Ayaz2011-01-091-3/+5
|
* Remove unused fun rebar_utils:get_os/0Tuncer Ayaz2011-01-091-20/+0
|
* Fix bug 770Tuncer Ayaz2011-01-081-2/+10
|
* Return more descriptive dependency errorsTuncer Ayaz2011-01-061-4/+7
|
* Use file:change_mode/2 instead of invoking chmodJuhani Rankimies2011-01-061-1/+3
|
* Unify executable invocationJuhani Rankimies2011-01-0610-96/+187
| | | | | Add flags to rebar_utils:sh to control output and error handling. Replace calls to os:cmd with calls to rebar_utils:sh.
* Fix error where ebin was created as a fileCharles McKnight2011-01-061-0/+1
| | | | | | | | | | | | | This patch remedies an issue where the ebin directory would be erroneously created as a file by the first "mv" command in rebar_protobuffs_compile.erl [line 106] if the ebin file did not exist at the root application level. In essence, the patch ensures that the ebin directory exists at the application directory level before any "mv" commands are executed. The following code was inserted at line 106: ok = filelib:ensure_dir(filename:join("ebin","dummy")),
* Fix order of erl_opts to be more accurateTuncer Ayaz2011-01-041-2/+2
|
* Remove erlc target after fail_on_warning failureJoseph Wayne Norton2010-12-271-0/+2
| | | | | Prevent overlooking a compilation warning by removing the target beam file after fail_on_warning failure.
* Add abnfc supportAnthony Ramine2010-12-221-0/+109
| | | | | | | | | abnfc is an ABNF parser generator. Options are: - doc_root (defaults to "src") - out_dir (defaults to "src") - source_ext (defaults to ".abnf") - module_ext (defaults to "")
* Support single level of nested template variablesDavid Reid2010-12-221-3/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add support for defining template variables of the following form: {variables, [{appid, "mochiwebapp"}, {author, "Mochi Media <dev@mochimedia.com>"}, {year, "2010"}, {version, "0.1"}, {port, 8080}, {dest, "{{appid}}"}]}. Where dest may be overridden on the commandline but will default to being the appid. Mochiweb uses this so that we can create new projects from the template in a configurable directory. So $ rebar create template=mochiwebapp dest=foo appid=bar I thought about special casing dest but figured it might be generally useful to be able to nest template vars. However this patch only does one level of resolution. So if {variables, [{foo, "{{bar}}"}, {bar, "{{foo}}"}]}. then bar will end up being the literal string {{bar}} and foo the literal string {{foo}}.
* Adding support for app_vars in external fileDave Smith2010-12-201-5/+23
|