aboutsummaryrefslogtreecommitdiffstats
path: root/lib/cosEventDomain
diff options
context:
space:
mode:
authorSiri Hansen <[email protected]>2012-09-17 12:27:05 +0200
committerSiri Hansen <[email protected]>2012-09-17 12:27:05 +0200
commit04c6b9a40f782099ece28dbde39c35f25dd2e37b (patch)
treef580dc9c18dbb948d771cbda65c1da57a9170a52 /lib/cosEventDomain
parent6a40b71e364fd0ac7f68bebfdd51c80f9f66730a (diff)
downloadotp-04c6b9a40f782099ece28dbde39c35f25dd2e37b.tar.gz
otp-04c6b9a40f782099ece28dbde39c35f25dd2e37b.tar.bz2
otp-04c6b9a40f782099ece28dbde39c35f25dd2e37b.zip
[reltool] Keep order from rel spec when sorting used and included applications
The rel specification now dictates the order in which included and used applications are loaded/started by the boot file. If the applications are not specified in the rel spec, then the order from the .app file is used. This was a bug earlier reported on systools, and is now also implemented in reltool. Example: If a .app file specified {applications,[x,y]} {included_applications,[b,c]} And the reltool.config has {rel, "myrel", "1.0", [a,y,x,c,b]} Then the boot file will load/start y before x and c before b. Earlier x would always be started before y and b always before c due to the order in the .app file.
Diffstat (limited to 'lib/cosEventDomain')
0 files changed, 0 insertions, 0 deletions