generate-appups giving errors when new application included in new release
ulf.wiger at erlang-solutions.com
Thu Mar 3 02:19:56 EST 2011
The tricky part here is to figure out what extra actions need to be performed in order to get the app propertly initialized. The 'setup' (http://github.com/esl/setup) application specifies "setup hooks" that can be picked up automatically, in order to create database tables, etc.
In the old AXD 301, we used to have corresponding "upgrade hooks" to specify what should be done during upgrade; these were read by our appup file generation program and used to generate an appropriate appup file.
On 3 Mar 2011, at 01:09, Fanjie Wang wrote:
> the app wasn't part of the previous release.
> On Mar 2, 2011, at 4:03 PM, Ken Ellis wrote:
>> Actually to clarify, by "new" do you mean the app wasn't part of the previous release, or was it a new version of an existing app.
>> On Mar 2, 2011 7:00 PM, "Ken Ellis" <kaellis at gmail.com> wrote:
>>> Check that the directory you removed had a .app file for the application.
>>> It needs to pull the vsn to determine whether the app needs to be part of
>>> the upgrade (the vsn has changed). That's where I usually see this error.
>>> On Mar 2, 2011 6:39 PM, "Fanjie Wang" <wangfanjie at gmail.com> wrote:
>>>> I'm running into an issue with "./rebar generate-appups" giving out error
>>> when the new generated release has a new application.
>>>> The error is:
>>>> $ ./rebar generate-appups previous_release=project_3
>>>> ==> rel (generate-appups)
>>>> ERROR: 'generate-appups' failed while processing /home/user/project/rel:
>>>> If I manually remove the new application from .../project/rel/project/lib
>>> folder, then "generate-appups" works.
>>>> Maybe I'm doing something wrong? Thanks for the help in advance!
>>>> rebar mailing list
>>>> rebar at lists.basho.com
> rebar mailing list
> rebar at lists.basho.com
Ulf Wiger, CTO, Erlang Solutions, Ltd.
More information about the rebar