Defect #10816
closed
Rails 3: Redmine doesn't load plugins tasks
0%
Description
When plugins were in /vendor/plugins and you ran rake, it looked to "./Rakefile" to loaded rake tasks.
Rakefile contained a line require 'tasks/rails'
And this line loaded all the rake tasks in /vendor/plugins/*/**/tasks/ directories:
http://stackoverflow.com/questions/417179/how-does-ruby-know-where-to-find-a-required-file
Now, nobody loads plugins tasks. When plugins were in /vendor/plugins things were so much easier. Why do you think that just changing plugins directory will help plugin maintainers to upgrade their plugins?
Updated by Jean-Philippe Lang about 12 years ago
- Category set to Plugin API
- Status changed from New to Closed
- Affected version (unused) set to devel
- Resolution set to Fixed
John Yani wrote:
When plugins were in /vendor/plugins and you ran rake, it looked to "./Rakefile" to loaded rake tasks.
Rakefile contained a linerequire 'tasks/rails'
And this line loaded all the rake tasks in/vendor/plugins/*/**/tasks/directories:
http://stackoverflow.com/questions/417179/how-does-ruby-know-where-to-find-a-required-fileNow, nobody loads plugins tasks.
I just missed it but it's fixed in r9615. Rake tasks from Redmine plugins are now loaded just as before.
It's not supposed to make the upgrade process easier but they were moved to /plugins for these 2 reasons:When plugins were in /vendor/plugins things were so much easier. Why do you think that just changing plugins directory will help plugin maintainers to upgrade their plugins?
- having Rails plugins used by the core and Redmine plugins mixed in the same directory was a mess. Some people were just copying the entire old content from vendor/plugins when upgrading
- having plugins in vendor/plugins is deprecated in Rails 3.2 and will be removed in a future Rails release