Hey, Indeed, I started work on that, mainly because of mountable applications (engines), but it can be used to generate any kind of rails extension. It's based on http://github.com/josevalim/enginex and the key difference in comparison to older plugins generator is that dummy application is generated in test/dummy (it can be configured with --dummy-path). This application is used to run the tests or during development to run server or console.
Cheers, Piotr On Dec 14, 6:37 am, PivotalBoulderMikeG <mgehard [email protected]> wrote: > Looks like someone has started to move down the gem route... > > https://github.com/rails/rails/commits/master/railties/lib/rails/gene... > > On Dec 10, 1:34 pm, Ryan Bigg <[email protected]> wrote: > > > > > > > > > Bundler comes with a gem generator: > > > bundle gem <gemname> > > > On 10/12/2010, at 22:49, Jack Kinsella <[email protected]> wrote: > > > > Full support with me on slowly deprecating the plugin system. It saves > > > new developers the cognitive load of asking "plugin vs gem". > > > > @Kevin > > > > Great idea with the "rails generate gem" addition. > > > > -- > > > Jack Kinsella > > > > On Dec 8, 5:34 pm, "James B. Byrne" <[email protected]> wrote: > > >> On Wed, December 8, 2010 11:31, Ernie Miller wrote: > > >>> On Dec 8, 2010, at 11:22 AM, Kevin Skoglund wrote: > > >>>> In a related tangent, I also wonder whether the lower-profile of > > >>>> plugins has caused vendor/* to lose its usefulness. Could > > >>>> everything > > >>>> in vendor/ move to lib/? It might just require some tweaks the > > >>>> autoloaded paths. lib/ could become the single directory for > > >>>> storing > > >>>> all non-application, non-Bundler, libraries of code. > > > >>> I find vendor to be a nice conventional place for various files that > > >>> our applications depend on, which should be version controlled > > >>> alongside our ruby code. The contents of vendor may not even be ruby > > >>> -- it might contain supporting software that's used in an > > >>> integration, for instance. > > > >>> Put another way, vendor is the place for third-party (vendor) > > >>> support files. > > > >> I agree. ./lib is mine, ./vendor is 'theirs'. > > > >> -- > > >> *** E-Mail is NOT a SECURE channel *** > > >> James B. Byrne mailto:[email protected] > > >> Harte & Lyne Limited http://www.harte-lyne.ca > > >> 9 Brockley Drive vox: +1 905 561 1241 > > >> Hamilton, Ontario fax: +1 905 561 0757 > > >> Canada L8E 3C3 > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "Ruby on Rails: Core" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]. > > > For more options, visit this group > > > athttp://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
