Make plugin generator consistent with gemplugins
Reported by Jacek Becela | June 30th, 2008 @ 06:28 PM | in 2.x
This is another patch (after #272 and others) which makes classic plugins and GemPlugins more alike. It changes plugin generator so it creates rails/init.rb instead of init.rb in main directory of a newly created plugin.
Comments and changes to this ticket
-
Jacek Becela July 1st, 2008 @ 07:35 AM
Should I also change locations of tasks and generators (move them into rails/ dir)? If you +1 this, be sure to take a look at #441 too.
-
Jacek Becela July 7th, 2008 @ 07:00 PM
- → Title changed from “Make plugin generator create rails/init.rb” to “Make plugin generator consistent with gemplugins”
I have uploaded new patch which also changes locations of tasks and generators to rails/tasks and rails/generators respectively.
-
-
Joshua Peek November 22nd, 2008 @ 07:52 PM
- → State changed from “new” to “stale”
Staling out, please let me know if its still an issue.
-
Jacek Becela November 22nd, 2008 @ 08:29 PM
Still the case,
ncr:~/dev/edge$ ./script/generate plugin foo create vendor/plugins/foo/lib create vendor/plugins/foo/tasks create vendor/plugins/foo/test create vendor/plugins/foo/README create vendor/plugins/foo/MIT-LICENSE create vendor/plugins/foo/Rakefile create vendor/plugins/foo/init.rb create vendor/plugins/foo/install.rb create vendor/plugins/foo/uninstall.rb create vendor/plugins/foo/lib/foo.rb create vendor/plugins/foo/tasks/foo_tasks.rake create vendor/plugins/foo/test/foo_test.rb -
Joshua Peek November 23rd, 2008 @ 06:33 AM
- → State changed from “stale” to “open”
-
DHH November 23rd, 2008 @ 12:45 PM
- → Assigned user changed from “” to “rick”
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
rick