In prior Rails versions, it used to be more challenging to create a stand-alone application without the entire file structure of Rails surrounding it, which is why the spec/dummy was in here in the first place. This is no longer the case, and this change removes the dummy app in favor of a smaller set of files which achieve the same result of providing a small footprint Rails app which the test suite can load the gem into, and run tests against an actual Rails app.
http://docs.travis-ci.com/user/workers/container-based-infrastructure/ With Container based CI, public projects can cache the results of bundle install
Allow a user to define which Rails engine to define routes on when using multiple engines within a Rails application. This will ensure that path helpers will correctly be available in the desired engine. This will default to the default main Rails application if another engine is not specified. Resolves issue [#138](#138)