#3797 Attempting to use engines results in failure - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#3797 ✓stale

Attempting to use engines results in failure

Reported by Ryan Bigg | January 27th, 2010 @ 02:19 PM

As I understand it, this may still be a work in progress. Raising a ticket anyway in case it isn't.

I have an engine located in vendor/plugins/train in an edge application. This train application is a clone of the edge application with application.rb modified so the Application class in it descends from Rails::Engine instead of Rails::Application and I have an init.rb file which requires this config/application.rb file. The reasoning for this last part is that before hand it was complaining of a uninitialized constant Train. config/application.rb loads this constant, so I thought this would be a quick&easy workaround to try and play with engines.

Alas, I get this error "train" is a Railtie/Engine and cannot be installed as plugin".

I do not know where engines are supposed to go apart from vendor/plugins. So what's up with this?

Comments and changes to this ticket

Ryan Bigg January 27th, 2010 @ 02:19 PM
- Tag changed from “engines” to “3.0pre, engines”
Rohit Arondekar June 23rd, 2010 @ 02:55 AM
This is still an issue on Rails master?
Santiago Pastorino February 2nd, 2011 @ 05:01 PM
- State changed from “new” to “open”
- Tag changed from “3.0pre, engines” to “30pre, engines”
- Importance changed from “” to “Low”
This issue has been automatically marked as stale because it has not been commented on for at least three months.

The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
Santiago Pastorino February 2nd, 2011 @ 05:01 PM
- State changed from “open” to “stale”
You flagged this item as spam.
klkk May 23rd, 2011 @ 02:59 AM
www.louisvuittonwarehouse.com