rebar3.git/test/upgrade_project/rel/files/nodetool, branch master Clone of https://github.com/erlang/rebar3 remove more code that can be brought back later if needed 2014-08-31T03:16:30+00:00 Tristan Sloughter t@crashfast.com 2014-08-31T03:14:48+00:00 21f47438614a0d50caf20801c4440d54d12c3f20 






Sync test/upgrade_project/rel/files with priv/templates
2013-06-12T15:01:57+00:00

Tuncer Ayaz
tuncer.ayaz@gmail.com

2013-06-12T14:57:26+00:00

500b62a890db84b233e8277e63a634bf2b157523












Clean up emacs file local variables
2011-01-31T16:55:36+00:00

Tuncer Ayaz
tuncer.ayaz@gmail.com

2011-01-31T16:43:31+00:00

c466076ffb5a1ea4c00d49fefff0dcfbceb58236












Update nodetool in upgrade_project
2011-01-31T16:55:02+00:00

Tuncer Ayaz
tuncer.ayaz@gmail.com

2011-01-31T16:55:02+00:00

1ee21c523fdf96d93f6d6a1f48ac6944ed5e47cf












Add 'generate-upgrade' command
2011-01-27T17:37:39+00:00

joewilliams
joe@joetify.com

2011-01-27T17:15:25+00:00

5298e93a180e6db87a33f26eb6a2db06e8065dc7

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.





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.