drnic / newgem

newgem - New Gem Generator for RubyGems — Read more

Sort by: Priority | Votes | Last Updated

Loading…

2.

0 votes

warning: couldn't activate the cucumber_features plugin, skipping
3 comments Created 6 months ago by hedgehog

Title

Body
1. I create a project using newgem (log is below) 2. run `rake features` and get the error: warning: couldn't activate the cucumber_features plugin, skipping Google indicates "cucumber_features" is pretty specific to newgem :) Appreciate any hits/tips. # newgem log exists create lib create script create lib/ffi-hdf create History.txt create Rakefile create README.rdoc create PostInstall.txt create lib/ffi-hdf.rb dependency install_rspec create spec create tasks create spec/ffi-hdf_spec.rb create spec/spec.opts create spec/spec_helper.rb create tasks/rspec.rake dependency install_website create website/javascripts create website/stylesheets create config exists script create website/index.txt create website/index.html create config/website.yml.sample create script/txt2html dependency plain_theme exists website/javascripts exists website/stylesheets create website/template.html.erb create website/stylesheets/screen.css create website/javascripts/rounded_corners_lite.inc.js dependency install_cucumber create features/step_definitions create features/support create features/development.feature create features/step_definitions/common_steps.rb create features/support/env.rb create features/support/common.rb create features/support/matchers.rb dependency install_rubigen_scripts exists script create script/generate create script/destroy create script/console create Manifest.txt readme readme Important ========= * Open Rakefile * Update missing details (gem description, dependent gems, etc.)
or cancel
1. I create a project using newgem (log is below)
2. run rake features and get the error:
  warning: couldn't activate the cucumber_features plugin, skipping
Google indicates "cucumber_features" is pretty specific to newgem :)
Appreciate any hits/tips.

newgem log
```
  exists  
  create  lib
  create  script
  create  lib/ffi-hdf
  create  History.txt
  create  Rakefile
  create  README.rdoc
  create  PostInstall.txt
  create  lib/ffi-hdf.rb
```
dependency install_rspec
```
  create    spec
  create    tasks
  create    spec/ffi-hdf_spec.rb
  create    spec/spec.opts
  create    spec/spec_helper.rb
  create    tasks/rspec.rake
```
dependency install_website
```
  create    website/javascripts
  create    website/stylesheets
  create    config
  exists    script
  create    website/index.txt
  create    website/index.html
  create    config/website.yml.sample
  create    script/txt2html
```
dependency plain_theme
```
  exists      website/javascripts
  exists      website/stylesheets
  create      website/template.html.erb
  create      website/stylesheets/screen.css
  create      website/javascripts/rounded_corners_lite.inc.js
```
dependency install_cucumber
```
  create    features/step_definitions
  create    features/support
  create    features/development.feature
  create    features/step_definitions/common_steps.rb
  create    features/support/env.rb
  create    features/support/common.rb
  create    features/support/matchers.rb
```
dependency install_rubigen_scripts
```
  exists    script
  create    script/generate
  create    script/destroy
  create  script/console
  create  Manifest.txt
  readme  readme
```
Important
- Open Rakefile
- Update missing details (gem description, dependent gems, etc.)
Comments

hedgehog Thu Jul 02 20:32:17 -0700 2009 | link

Moved to lighthouse ticketing system:

http://drnic.lighthouseapp.com/projects/18881-newgem/tickets/20-warning-couldnt-activate-the-cucumber_features-plugin-skipping

Comment
Moved to lighthouse ticketing system: http://drnic.lighthouseapp.com/projects/18881-newgem/tickets/20-warning-couldnt-activate-the-cucumber_features-plugin-skipping
or cancel

drnic Mon Nov 02 15:04:49 -0800 2009 | link

Is this still an issue? I think the hoe plugin is cucumberfeatures now

Comment
Is this still an issue? I think the hoe plugin is cucumberfeatures now
or cancel

hedgehog Mon Nov 02 16:41:03 -0800 2009 | link

Works for me right now. Thanks

Comment
Works for me right now. Thanks
or cancel

Parsed with GitHub Flavored Markdown
3.

0 votes

Newgem won't install on Ruby 1.9.1
1 comment Created 5 months ago by rrouse

Title

Body
RedCloth fails to build because you have a specific version specified as dependant. That version does not build on Ruby 1.9.1, but later versions do (4.2.2 for example). Can you please change or remove that dependency?
or cancel

RedCloth fails to build because you have a specific version specified as dependant. That version does not build on Ruby 1.9.1, but later versions do (4.2.2 for example).

Can you please change or remove that dependency?

Comments

drnic Tue Aug 04 15:12:08 -0700 2009 | link

Fixed in 1.5.2

Comment
Fixed in 1.5.2
or cancel

Parsed with GitHub Flavored Markdown
6.

0 votes

new generator
x

[Wishlist] RSpec+RCov Support
1 comment Created 2 months ago by claco

Title

Body
First, I'm a total Ruby/Rails/RSpec/rCov Newb, so be kind. :-) I've been using newgem to create a new project every time I start working on a new code kata in Ruby. While there's a nice option for rspec support, I find myself always trying to run rake rcov, which does nothing for spec tests, then fumbling on the net to find a rake task. Here's the rake task I usually find and apply. If would be nice if this was either generated when the rspec options were used, or there was another option to do so. begin require 'rcov' rescue LoadError require 'rubygems' unless ENV['NO_RUBYGEMS'] require 'rcov' end "Run all specs with rcov and store coverage report in doc/output/coverage" Spec::Rake::SpecTask.new(:spec_rcov) do |t| t.spec_files = FileList['spec/**/*.rb'] t.rcov = true t.rcov_dir = 'doc/output/coverage' t.rcov_opts = ['-t --exclude', 'spec,\.autotest,rcov.rb'] end
or cancel
First, I'm a total Ruby/Rails/RSpec/rCov Newb, so be kind. :-)

I've been using newgem to create a new project every time I start working on a new code kata in Ruby. While there's a nice option for rspec support, I find myself always trying to run rake rcov, which does nothing for spec tests, then fumbling on the net to find a rake task.

Here's the rake task I usually find and apply. If would be nice if this was either generated when the rspec options were used, or there was another option to do so.
```
begin
  require 'rcov'
rescue LoadError
  require 'rubygems' unless ENV['NO_RUBYGEMS']
  require 'rcov'
end

"Run all specs with rcov and store coverage report in doc/output/coverage"
Spec::Rake::SpecTask.new(:spec_rcov) do |t|
  t.spec_files = FileList['spec/**/*.rb']
  t.rcov = true
  t.rcov_dir = 'doc/output/coverage'
  t.rcov_opts = ['-t --exclude', 'spec,\.autotest,rcov.rb']
end
```
Comments

drnic Mon Nov 02 15:42:24 -0800 2009 | link

If you upgrade to hoe 2.3.3, it has rcov already built in. So all your projects should have a "rake rcov" task.

If you don't like their rcov task (http://github.com/seattlerb/hoe/blob/a05c7ab9610ae1c6dba27df7cded5f7689d5ab8c/lib/hoe/rcov.rb) perhaps fork hoe and extend the hoe plugin there for your tastes?

Comment
If you upgrade to hoe 2.3.3, it has rcov already built in. So all your projects should have a "rake rcov" task. If you don't like their rcov task (http://github.com/seattlerb/hoe/blob/a05c7ab9610ae1c6dba27df7cded5f7689d5ab8c/lib/hoe/rcov.rb) perhaps fork hoe and extend the hoe plugin there for your tastes?
or cancel

Parsed with GitHub Flavored Markdown
1.

1 vote

documentation
x

Updates due on newgem.rubyforge.org
1 comment Created 8 months ago by svoop

Title

Body
Great gem, however, the prose on newgem.rubyforge.org is slightly out of date. In the "Setup" section, you still refer to "config/hoe.rb" for configuration, but that's in the "Rakefile" now.
or cancel

Great gem, however, the prose on newgem.rubyforge.org is slightly out of date. In the "Setup" section, you still refer to "config/hoe.rb" for configuration, but that's in the "Rakefile" now.

Comments

drnic Wed Jun 17 02:47:41 -0700 2009 | link

Yeah, probably a few website + README updates due with 1.5.0 release (soon)

Comment
Yeah, probably a few website + README updates due with 1.5.0 release (soon)
or cancel

Parsed with GitHub Flavored Markdown
4.

0 votes

bug
x

Trouble generating website using newgem
0 comments Created 5 months ago by rleber

Title

Body
I am having trouble getting the website to generate. script/generate install_website ... uninitialized constant InstallWebsiteGenerator::Newgem rake website_generate ... ruby: No such file or directory -- script/txt2html (LoadError) See example at http://gist.github.com/153279
or cancel

I am having trouble getting the website to generate.

script/generate install_website

...

uninitialized constant InstallWebsiteGenerator::Newgem

rake website_generate

...

ruby: No such file or directory -- script/txt2html (LoadError)

See example at
http://gist.github.com/153279

Comments

Parsed with GitHub Flavored Markdown
5.

0 votes

bug
x

Empty line in manifest declares non existing file in gemspec
1 comment Created 5 months ago by maca

Title

Body

or cancel

Comments

drnic Mon Nov 02 15:03:18 -0800 2009 | link

Is this a bug in the gem or generated gems? Sorry if I knew this issue and have forgotten the problem

Comment
Is this a bug in the gem or generated gems? Sorry if I knew this issue and have forgotten the problem
or cancel

Parsed with GitHub Flavored Markdown
7.

0 votes

couple test issues
0 comments Created 3 days ago by mdkent

Title

Body
Using Debian's version of rake rubygems isn't already loaded resulting in <pre> mkent@fortaleza:~/.gem/ruby/1.8/gems/newgem-1.5.2$ rake -T (in /home/mkent/.gem/ruby/1.8/gems/newgem-1.5.2) rake aborted! undefined method `gem' for main:Object /home/mkent/.gem/ruby/1.8/gems/newgem-1.5.2/Rakefile:1 (See full trace by running task with --trace) mkent@fortaleza:~/.gem/ruby/1.8/gems/newgem-1.5.2$ </pre> possible to add "require 'rubygems'" prior to 'gem'? Also there appears to be one failing test: <pre> 1) Failure: test_newgem(TestNewgemGenerator) [/usr/lib/ruby/gems/1.8/gems/rubigen-1.5.2/lib/rubigen/helpers/generator_test_helper.rb:58:in `assert_directory_exists' ./test/test_newgem_generator.rb:21:in `test_newgem']: The directory 'tasks' should exist. <false> is not true. </pre> looking at the newgem generator I'm guessing the assert is unnecessary?
or cancel
Using Debian's version of rake rubygems isn't already loaded resulting in
```
mkent@fortaleza:~/.gem/ruby/1.8/gems/newgem-1.5.2$ rake -T
(in /home/mkent/.gem/ruby/1.8/gems/newgem-1.5.2)
rake aborted!
undefined method `gem' for main:Object
/home/mkent/.gem/ruby/1.8/gems/newgem-1.5.2/Rakefile:1
(See full trace by running task with --trace)
mkent@fortaleza:~/.gem/ruby/1.8/gems/newgem-1.5.2$
```
possible to add "require 'rubygems'" prior to 'gem'?

Also there appears to be one failing test:
```
  1) Failure:
test_newgem(TestNewgemGenerator)
    [/usr/lib/ruby/gems/1.8/gems/rubigen-1.5.2/lib/rubigen/helpers/generator_test_helper.rb:58:in `assert_directory_exists'
     ./test/test_newgem_generator.rb:21:in `test_newgem']:
The directory 'tasks' should exist.
 is not true.
```
looking at the newgem generator I'm guessing the assert is unnecessary?
Comments

Parsed with GitHub Flavored Markdown