* RedCloth dependency - changed to new 4.0.0 version which is apparently new a shiny + fast
…s). Files are actually in the spec directory (no s)
… class by loading and evaling the file. Useful for generic rake tasks where one might want to avoid knowing the classname and file path.
…since github makes them look pretty; hoe patch on the way so hoe supports it
For those of us with catch-all--type projects on Rubyforge (cf. copiousfreetime, codeforpeople, or *ahem* yomendel), it's not entirely helpful that the gem name and project name are the same in the generated files. This allows an override with a command-line argument, but keeps the gem name as the default.
… username. Newgem::Rubyforge#rubyforge was missing a call to RubyForge#configure, which left the userconfig attribute as a string instead of making it a hash. This was a bit of a testing adventure, what with the constant-setting and all. It'd be easier with more TDD.
…'t get test folder
* --simple template * Make LICENSE, Rakefile, and README templates * LICENSE uses the current year * README is a real template with the name of the app inside * Rakefile sets GEM= the name of the app * Use GEM_VERSION instead of VERSION to quiet a warning * Jump to 0.23.2