Nested applications and dependancies about exrm

[bitwalker]

So it looks like even though ERTS is packaged in to the release, all applications that need to be bundled need to be defined in the release configuration. Relx handles this transparently normally, but the problem seems to be that if the dependencies aren't specified in the application config generated by mix or rebar, then Relx doesn't know to pull those in to the release configuration.

I'm looking in to maybe allowing users to request bundling ALL Erlang applications be bundled if so desired, but before I go down that road, I'd like if you could take some time and build me a minimal example of an app which uses :eldap, which still produces the problem you are seeing. Then I can play around with the release configuration stuff a bit to see what settings might be friendlier for building a release for something where not all the dependencies are properly configured.

I'm available in IRC all weekend, so ping me if you're around, and we can talk more.

[bitwalker]

I've updated all documentation to reflect the need for all transitive application dependencies to be defined in either the top-level project's mix.exs, or any of the dependencies' mix.exs, rebar.config, or app.config files.

There are some hacky ways to add all Erlang applications to a release, but the problem is that when a release boots, every single application it depends on is also started. To include all standard library applications would be a huge waste of resources, and would likely be a pretty large performance hit, so for now I'm not going to pursue making that an optional feature. After reading up on Erlang releases some more, it's pretty clear that application dependencies must be defined in order for a release to work properly, so I don't see any way around that requirement.