Fixed the loading order of an app's dependencies.

[dariocravero]

If we load apps first, libraries won't be there, hence throwing exceptions at run time.
For example, this can be reproduced with any library that needs to be registered like ScssInitialiazer.
See #1448#issuecomment-26143346. This bug was introduced with this commit

/cc @ujifgc @padrino/core-members

[ujifgc]

Does it trip here loader.rb#L60 dependency_paths.each{ |path| require_dependencies(path) }?

Can you try broken order with require_dependencies(*dependency_paths)?

[dariocravero]

@ujifgc that works alright :). I just get informed of the missing constant though which might be a bit annoying for users? See:

  DEBUG -   LOADING (0.0123s) /.../app/app.rb
  ERROR -  NameError: uninitialized constant MyApp::App::ScssInitializer; /.../app/app.rb:3:in `<class:App>'
  DEBUG -   LOADING (0.0123s) /.../lib/mobile_de.rb

Is there any particular reason why you put config/apps.rb on top?

[ujifgc]

Yeah, there's one alphabetic reason, LOL.

[ujifgc]

I think we should keep both fixes: yours with apps.rb on bottom and the launch of circular loader.

[dariocravero]

Sounds good to me :)