rebar3.git - Clone of https://github.com/erlang/rebar3

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add support for using -remsh via runner script	joewilliams	2012-04-23	2	-7/+81
\|
*	Handle vm.args properly while building upgrades	joewilliams	2011-10-05	1	-24/+23
\| \| \| \| \| \| \|	This patch corrects the vm.args behavior while building upgrade tarballs by copying the file from the release into the upgrade. Additionally it patches the dummy runner script in the upgrade test project to work properly.
*	Get rid of app.config	joewilliams	2011-09-20	3	-4/+17
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	app.config has been a long standing erroneous file in rebar. Erlang/OTP documentation suggests a sys.config file instead. This file is stored in the releases/VSN directory. This does a few things but most importantly it ensures your config (contained in the application environment) survives a hot upgrade. It also has the advantage of allowing the configuration of the application to be versioned along side the application code. This patch flips rebar to use sys.config rather than app.config. Additionally it makes this flip to vm.args as well, making them versioned just like sys.config. This patch also includes runner script changes to support the old etc/app.config config file location and support for Windows. Thanks to mokele for the initial work and kick in the pants to make this finially happen.
*	Sync rel/files in dummy project with templates	Tuncer Ayaz	2011-07-18	4	-11/+29
\|
*	Update runner script in test project	Tuncer Ayaz	2011-03-04	1	-3/+3
\|
*	Clean up emacs file local variables	Tuncer Ayaz	2011-01-31	1	-1/+1
\|
*	Update nodetool in upgrade_project	Tuncer Ayaz	2011-01-31	1	-0/+22
\|
*	Add 'generate-upgrade' command	joewilliams	2011-01-27	6	-0/+360
	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.