twp / bones Goto Github PK

flame@yamato bones % ruby19 -I../bones-extras/lib -S rake spec:specdoc
(in /media/repos/flame/ruby/bones)
There is an error on line 16 of your Rakefile:

    undefined method `name' for nil:NilClass
    [16]   rubyforge.name 'codeforpeople'

Please ensure required gems are installed, otherwise Mr Bones will
not generate default configuration settings and values. This can lead
to undefined method errors on nil values.

This does not happen with either Ruby 1.8 or JRuby, so I have no idea where the problem lies :/

I'm new to using github so I hope this is what you need:

bones version 3.7.0:
I found one deprecation warning for RSpec:
DEPRECATION WARNING: you are using deprecated behaviour that will be
removed from a future version of RSpec. /tmp/wookie/spec/spec_helper.rb:
5:in `' * Spec::Runner.configure is deprecated. * please use
RSpec.configure instead.

In spec_helper.rb changing "Spec::Runner.configure" to "RSpec.configure"
removed the warning.

I'm using:
rspec (2.6.0)
rspec-core (2.6.3)
rspec-expectations (2.6.0)
rspec-mocks (2.6.0)
rspec-rails (2.6.1, 2.6.0)

and
ruby 1.9.2p180

**Leigh

The reasoning here is that "x.y.z" being equivalent to "= x.y.z" is what RubyGems does (both in gemspecs and on the command line). For instance, if I say gem install activerecord -v 2.3.5, I expect 2.3.5 to be installed and not 3.0.whatever.

(Placing this here as a reminder to myself)

I'm seeing odd characters when I run the various bones commands. I'm not sure if its coming from bones, rake, or the two playing badly together. Any ideas?

ruby 1.8.7
bones 3.7.0
rake 0.9.2

bones info
The default project skeleton will be copied from:
←[36mC:/Ruby187/lib/ruby/gems/1.8/gems/bones-3.7.0/default←[0m

rake bones:options
←[33m - ←[0m←[37mann.email.authtype←[0m
←[33m - ←[0m←[37mann.email.domain←[0m
←[33m - ←[0m←[37mann.email.from←[0m
←[33m - ←[0m←[37mann.email.password←[0m
←[33m - ←[0m←[37mann.email.port←[0m
←[33m - ←[0m←[37mann.email.server←[0m
←[33m - ←[0m←[37mann.email.to←[0m
←[33m - ←[0m←[37mann.email.username←[0m
←[33m - ←[0m←[37mann.file←[0m
←[33m - ←[0m←[37mann.paragraphs←[0m
←[33m - ←[0m←[37mann.text←[0m
←[33m - ←[0m←[37mauthors←[0m
←[33m - ←[0m←[37mchanges←[0m
←[33m - ←[0m←[37mcolorize←[0m
←[33m - ←[0m←[37mdescription←[0m
←[33m - ←[0m←[37memail←[0m
←[33m - ←[0m←[37mexclude←[0m
←[33m - ←[0m←[37mgem._spec←[0m
←[33m - ←[0m←[37mgem.dependencies←[0m
←[33m - ←[0m←[37mgem.development_dependencies←[0m

cremes$ gem install bones
ERROR: Error installing bones:
bones requires bones-git (>= 1.1.2, runtime)

cremes$ gem install bones-git bones bones-extras
ERROR: Error installing bones-git:
bones-git requires bones (>= 3.4.2, runtime)
ERROR: Error installing bones:
bones requires bones-git (>= 1.1.2, runtime)
ERROR: Error installing bones-extras:
bones-extras requires bones (>= 3.4.3, runtime)

Hello

I'm having this problem. I did a fresh installation of bones using gems on an Ruby 1.8.7 environment. I have rake 0.8.7 and I create a new bones-project. When I do rake -T I get this message and rake is aborted.

uninitialized constant Rake::DSL

If I do the same on a Ruby 1.9.2 environment and the same rake version it works fine.

On both environments I installed bones 3.7.1. I had a look on pre-existing issues, there was #20 which concerns rake >= 0.9. Is my related?

Thank you!
Dahie

When running rake bones:options or rake bones:help on Windows the printout contains color escaping for Unix. This makes the information unreadable.

A Rakefile generate by Bones 3.7.2 will not load at all if the RDoc gem is not installed.

$ rake -T --trace
rake aborted!
can't convert Loquacious::Undefined into String
gems/bones-3.7.2/lib/bones/plugins/rdoc.rb:49:in `escape'
gems/bones-3.7.2/lib/bones/plugins/rdoc.rb:49:in `post_load'

Inserting the following in a default rake file from bones 3.7.1 doesn't seem to use the options.
spec = config.gem._spec

spec.rdoc_options << [ "-all", "--tab-width=4" ]

I have tried MANY different ways to set these options without success.

Running rdoc directly on my system does accept these options and use them.
Is this a bug or am I missing the correct way to provide these options?

Thanks,
Dave

Just discovering bones, and I'm having trouble building my gem:

WARNING: licenses is empty, but is recommended. Use a license identifier from
http://spdx.org/licenses or 'Nonstandard' for a nonstandard license.
WARNING: description and summary are identical
WARNING: open-ended dependency on bones (>= 3.8.4, development) is not recommended
if bones is semantically versioned, use:
add_development_dependency 'bones', '~> 3.8', '>= 3.8.4'`

So far, I have been unable to find out what parameters were allowed in the Rakefile.
Adding a 'licenses' is simply ignored.
I don't know where bones gets the description and summary from.
Adding "depend_on 'bones', '~> 3.8', :development => true" to the Rakefile causes a blocking error:

Gem::InvalidSpecificationException: duplicate dependency on bones (>= 3.8.4, development), (> 3.8) > use:
add_development_dependency 'bones', '>= 3.8.4', '> 3.8'

Help a newbie out? If you want to have a look at my gem to tell me what I did wrong: https://github.com/cornuwel/nvidia-smi

When executing 'rake gem:spec', it interrogates various files and builds a new gemspec. Oftentimes the gem in question has dependencies on external gems. Right now there is no programmatic way to add these dependencies to the project.

Ideally, the Rakefile "Bones" block could be edited (as it is now for modifying the readme_file name, etc.) to list a set of dependencies. Subsequent runs of 'rake gem:spec' would pick up these dependencies and add them to the gemspec.

When I run create I get
$ bones create aoeu
Created 'aoeu'
Now you need to fix these files
(in /tmp/aoeu)
rake aborted!
(eval):1:in remove_method': methodnamespace' not defined in Module
/tmp/aoeu/Rakefile:14
(See full trace by running task with --trace)

It seems yard has fixed the problem mentioned here:

# FIXME This is a monkey-patch till yard fixes the namespace method collision
Module.class_eval 'remove_method :namespace'

Thanks for looking at this

Hi,

I'm building a gem and i'd like to use bones via its ruby API to implement some features. My goal is build a pry-plugin_kit plugin for the Pry REPL. To that end, i'd like the user to be able to type pry --build_plugin my_plugin and it'll use a bones template stored in the gem's directory.

Currently if i want this functionality, i have to get the user to manually copy the bones skeleton to their ~/.mrbones/ directory, right? It woudl be much nicer if i could just tell the bones gem to create a project from a skeleton stored in a directory of my choosing, and nicer still if i could do that without shelling out :P Anyway, let me know what u think.

thanks

After installing bines 3.2.0 as a gem, running "bones create foobar" gives errors:

Error loading "/usr/local/lib/ruby/gems/1.8/gems/bones-2.3.1/lib/bones/app/unfreeze_command.rb": App is not a class. skipping...
Error loading "/usr/local/lib/ruby/gems/1.8/gems/bones-2.3.1/lib/bones/app/info_command.rb": App is not a class. skipping...

Removing that version just changes the error; bones seems t want to load the highest gem lib that is not 3.2.0.

Tried hard-coding the version string into the bones script, but makes no difference.

It would be nice if bones could have a "release and advance" functionality similar to that of Maven.

The "release and advance" functionality for gem foobar VERSION=0.1 would do something like

• tag the git repository with git tag -s -v0.1 -m "foobar v0.1",
• prepare the gem,
• push the gem,
• ask for the new version number (in this case 0.2),
• change version in Rakefile to 0.2,
• commit the change with git commit -a -m "Prepare for foobar next development iteration (v0.2)".

RubyGems 2.0.0 removed Gem::Builder in favor of Gem::Package, so bones will need to be updated to work on newer RubyGems.

Using JRuby version 1.7.5 I get:

% jirb
irb(main):001:0> require 'bones'
LoadError: no such file to load -- rubygems/builder
        from org/jruby/RubyKernel.java:1082:in `require'
        from /export/pack/jruby-1.7.5-di/x86_64-Linux-2.6/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:53:in `require'
        from /export/pack/jruby-1.7.5-di/x86_64-Linux-2.6/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:51:in `require'
        from /home/davei/.gem/jruby/1.9/gems/bones-3.8.1/lib//bones/gem_package_task.rb:8:in `(root)'
        from org/jruby/RubyKernel.java:1082:in `require'
        from /export/pack/jruby-1.7.5-di/x86_64-Linux-2.6/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:53:in `require'
        from /export/pack/jruby-1.7.5-di/x86_64-Linux-2.6/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:51:in `require'
        from /home/davei/.gem/jruby/1.9/gems/bones-3.8.1/lib/bones.rb:1:in `(root)'
        from /home/davei/.gem/jruby/1.9/gems/bones-3.8.1/lib/bones.rb:91:in `(root)'
        from /home/davei/.gem/jruby/1.9/gems/bones-3.8.1/lib/bones.rb:58:in `libpath'
        from org/jruby/RubyKernel.java:1082:in `require'
        from /home/davei/.gem/jruby/1.9/gems/bones-3.8.1/lib/bones.rb:87:in `(root)'
        from /export/pack/jruby-1.7.5-di/x86_64-Linux-2.6/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:1:in `(root)'
        from org/jruby/RubyKernel.java:1121:in `eval'
        from /export/pack/jruby-1.7.5-di/x86_64-Linux-2.6/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:133:in `require'
        from (irb):1:in `evaluate'
        from org/jruby/RubyKernel.java:1517:in `loop'
        from org/jruby/RubyKernel.java:1282:in `catch'
        from org/jruby/RubyKernel.java:1282:in `catch'
        from /usr/pack/jruby-1.7.5-di/x86_64-Linux-2.6/bin/jirb:13:in `(root)'irb

A fix for the problem is to modify gem_package_task.rb this way:

...
# dmi code
#if RUBY_VERSION >= "2"
#  require 'rubygems/package'
#else
#  require 'rubygems/builder'
#end
begin
    # for ruby 2.0 or jruby 1.7.5 
    require 'rubygems/package'
rescue LoadError
    require 'rubygems/builder'
end
# end dmi code
...

I'll yield to others with greater knowledge of compatibility issues for any
other form of fix, but the above seems to work for me.

Running:

bones plugins --all

under Ruby version 2.0.0 and 2.1.0 results in:

Looking up avaialble Mr Bones plugins ... ERROR: While executing bones ... (NoMethodError)
undefined method `find_matching' for #Gem::SpecFetcher:0x007fe35fa113d8

Other functionality seems to be fine. I was able to successfully create a project. It's just the plugin listing that fails.

I'm a ruby newb so I accept that this may be something really simple, and I apologize in advance if I'm simply being dumb.

I am running Xubuntu 13.10, rbenv with version 1.9.3, 2.0.0, and 2.1.0 and bones 3.8.1.

Trying to work on aspen (http://github.com/kevwil/aspen) which uses bones and is developed in JRuby.

After installing bones successfully running rake failed:

$ jruby -S rake -T
(in /Users/stephen/dev/ruby/src/gems/aspen-git)
### Please install the "bones" gem ###

The error is actually caused because the git gem is not installed.

Details ...

Running JRuby 1.4

$ jruby --version
jruby 1.4.0 (ruby 1.8.7 patchlevel 174) (2009-12-06 731d38d) (Java HotSpot(TM) Client VM 1.5.0_20) [i386-java]

Installed bones v3.1.2 -- though had to run install three times before succeeding, first install told me I needed little-plugger, second try told me I needed loquacious, third try worked.

$ jruby -S gem list bones

*** LOCAL GEMS ***

bones (3.1.2)

Running bones --help shows the error clearly:

$ jruby -S bones --help
/Users/stephen/dev/test/jruby-git/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require': no such file to load -- git (LoadError)
    from /Users/stephen/dev/test/jruby-git/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
    from /Users/stephen/dev/test/jruby-git/lib/ruby/gems/1.8/gems/bones-3.1.2/lib/bones.rb:10
    from /Users/stephen/dev/test/jruby-git/lib/ruby/gems/1.8/gems/bones-3.1.2/lib/bones.rb:31:in `require'
    from /Users/stephen/dev/test/jruby-git/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
    from /Users/stephen/dev/test/jruby-git/lib/ruby/gems/1.8/gems/bones-3.1.2/bin/bones:8
    from /Users/stephen/dev/test/jruby-git/lib/ruby/gems/1.8/gems/bones-3.1.2/bin/bones:19:in `load'
    from /Users/stephen/dev/test/jruby-git/bin/bones:19

Installing the bones-git plugin fixes the issue (but what actually fixes the issue is the install of the dependent gem: 'git'.

$ jruby -S gem install bones-git
Successfully installed git-1.2.5
Successfully installed bones-git-1.1.1
2 gems installed
Installing ri documentation for git-1.2.5...
Installing ri documentation for bones-git-1.1.1...
Updating ri class cache with 3966 classes...
Installing RDoc documentation for git-1.2.5...
Installing RDoc documentation for bones-git-1.1.1...

Now bones can print it's help without error:

$ jruby -S bones --help
NAME
  bones v3.1.2

DESCRIPTION
  Mr Bones is a handy tool that builds a skeleton for your new Ruby
  projects. The skeleton contains some starter code and a collection of
  rake tasks to ease the management and deployment of your source code.

  Usage:
    bones -h/--help
    bones -v/--version
    bones command [options] [arguments]

  Examples:
    bones create new_project
    bones freeze -r git://github.com/fudgestudios/bort.git bort
    bones create -s bort new_rails_project

  Commands:
    bones create          create a new project from a skeleton
    bones freeze          create a new skeleton in ~/.mrbones/
    bones unfreeze        remove a skeleton from ~/.mrbones/
    bones info            show information about available skeletons

  Further Help:
    Each command has a '--help' option that will provide detailed
    information for that command.

    http://github.com/TwP/bones

I can uninstall the bones-git and bones still keeps working because the git gem is still installed:

$ jruby -S gem uninstall bones-git

You have requested to uninstall the gem:
    bones-git-1.1.1
bones-3.1.2 depends on [bones-git (>= 1.1.1)]
little-plugger-1.1.1 depends on [bones-git (>= 1.0.0)]
loquacious-1.4.1 depends on [bones-git (>= 1.1.1)]
If you remove this gems, one or more dependencies will not be met.
Continue with Uninstall? [Yn]  y
Successfully uninstalled bones-git-1.1.1
$ jruby -S bones --help
NAME
  bones v3.1.2

DESCRIPTION
  Mr Bones is a handy tool that builds a skeleton for your new Ruby
  projects. The skeleton contains some starter code and a collection of
  rake tasks to ease the management and deployment of your source code.

  Usage:
    bones -h/--help
    bones -v/--version
    bones command [options] [arguments]

  Examples:
    bones create new_project
    bones freeze -r git://github.com/fudgestudios/bort.git bort
    bones create -s bort new_rails_project

  Commands:
    bones create          create a new project from a skeleton
    bones freeze          create a new skeleton in ~/.mrbones/
    bones unfreeze        remove a skeleton from ~/.mrbones/
    bones info            show information about available skeletons

  Further Help:
    Each command has a '--help' option that will provide detailed
    information for that command.

    http://github.com/TwP/bones

flame@yamato bones % rake -D
(in /media/repos/flame/ruby/bones)
There is an error on line 17 of your Rakefile:

    undefined method `name' for nil:NilClass
    [17]   rubyforge.name 'codeforpeople'

Please ensure required gems are installed, otherwise Mr Bones will
not generate default configuration settings and values. This can lead
to undefined method errors on nil values.

I have rubyforge gem installed, by the way. I'm not sure what is causing this exactly.

The docs for bones say there are no requirements, but "sudo gem i bones" fails if you have not already installed little-plugger and loquacious. The bones gem does not try to install these for you; it just complains and exits.

In bones version 3.8.4, a warning is issued in ruby >= 2.7 upon running 'rake test'

rake test
NOTE: Gem::Specification#rubyforge_project= is deprecated with no replacement. It will be removed on or after 2019-12-01.
Gem::Specification#rubyforge_project= called from /usr/local/lib/ruby/gems/2.7.0/gems/bones-3.8.4/lib/bones/plugins/gem.rb:152.

The following patch to lib/bones/plugins/gem.rb fixes the problem:

--- gem.rb	2020-06-20 17:10:04.000000000 -0700
+++ /tmp/gem.rb	2020-06-20 17:29:52.000000000 -0700
@@ -149,12 +149,10 @@
           s.authors = Array(config.authors)
           s.email = config.email
           s.homepage = Array(config.url).first
-          if s.methods.include?(:rubyforge_project)
-            s.rubyforge_project = config.name
+          s.rubyforge_project = config.name
 
-            if !config.rubyforge.nil? and config.rubyforge.name
-              s.rubyforge_project = config.rubyforge.name
-            end
+          if !config.rubyforge.nil? and config.rubyforge.name
+            s.rubyforge_project = config.rubyforge.name
           end
 
           s.description = config.description

A rake -T command on this simple Rakefile fails with a undefined method 'namespace' for Bones::Plugins::Ann:Module error.

require 'bones'

Bones  {
    name 'example'
}

I'm using Bones 3.6.5 installed via Rubygems. I also tested RVM + Ruby 1.9.2 + Rubygems.

This is the complete stack trace

$ rake -T --trace
rake/rdoctask is deprecated.  Use rdoc/task instead (in RDoc 2.4.2+)
rake aborted!
undefined method `namespace' for Bones::Plugins::Ann:Module
.../gems/gems/bones-3.6.5/lib/bones/plugins/ann.rb:94:in `define_tasks'
.../gems/gems/bones-3.6.5/lib/bones.rb:129:in `Bones'
.../gems/gems/bones-3.6.5/lib/bones.rb:129:in `each'
.../gems/gems/bones-3.6.5/lib/bones.rb:129:in `Bones'
/tmp/ns-fail/Rakefile:3
.../gems/gems/rake-0.9.0/lib/rake/rake_module.rb:25:in `load'
.../gems/gems/rake-0.9.0/lib/rake/rake_module.rb:25:in `load_rakefile'
.../gems/gems/rake-0.9.0/lib/rake/application.rb:495:in `raw_load_rakefile'
.../gems/gems/rake-0.9.0/lib/rake/application.rb:78:in `load_rakefile'
.../gems/gems/rake-0.9.0/lib/rake/application.rb:129:in `standard_exception_handling'
.../gems/gems/rake-0.9.0/lib/rake/application.rb:77:in `load_rakefile'
.../gems/gems/rake-0.9.0/lib/rake/application.rb:61:in `run'
.../gems/gems/rake-0.9.0/lib/rake/application.rb:129:in `standard_exception_handling'
.../gems/gems/rake-0.9.0/lib/rake/application.rb:59:in `run'
.../gems/gems/rake-0.9.0/bin/rake:31
.../gems/bin/rake:19:in `load'
.../gems/bin/rake:19

Hi Tim :)

Here's what happens, for instance, when trying to install a gem called "simplemock" (the actual gem name is "simple_mock"):

☃ rake gem:install_dependencies --trace
** Invoke gem:install_dependencies (first_time)
** Invoke gem:prereqs (first_time)
** Execute gem:prereqs
** Execute gem:install_dependencies
Installing simplemock
rake aborted!
undefined method `full_name' for nil:NilClass
/Users/elliot/.rbenv/versions/1.9.3-p125/lib/ruby/1.9.1/rubygems/dependency_installer.rb:136:in `block in gather_dependencies'
/Users/elliot/.rbenv/versions/1.9.3-p125/lib/ruby/1.9.1/rubygems/dependency_installer.rb:136:in `map'
/Users/elliot/.rbenv/versions/1.9.3-p125/lib/ruby/1.9.1/rubygems/dependency_installer.rb:136:in `gather_dependencies'
/Users/elliot/.rbenv/versions/1.9.3-p125/lib/ruby/1.9.1/rubygems/dependency_installer.rb:267:in `install'
/Users/elliot/.rbenv/versions/1.9.3-p125/lib/ruby/gems/1.9.1/gems/bones-3.8.0/lib/bones/plugins/gem.rb:287:in `block (3 levels) in define_tasks'
/Users/elliot/.rbenv/versions/1.9.3-p125/lib/ruby/gems/1.9.1/gems/bones-3.8.0/lib/bones/plugins/gem.rb:278:in `each'
/Users/elliot/.rbenv/versions/1.9.3-p125/lib/ruby/gems/1.9.1/gems/bones-3.8.0/lib/bones/plugins/gem.rb:278:in `block (2 levels) in define_tasks'

I can look into this later if you like...

The project is lacking a Gemfile to specify dependencies. Adding one may help folks get running more quickly.

%sudo macgem install bones

This works fine, but trying to run bones after the install gives me an error.

%bones --help

Output:

/Library/Frameworks/MacRuby.framework/Versions/0.8/usr/lib/ruby/Gems/1.9.2/gems/rake-0.8.7/lib/rake.rb:2503:in const_missing:': uninitialized constant Bones::App::Plugins (NameError) from /Library/Frameworks/MacRuby.framework/Versions/0.8/usr/lib/ruby/Gems/1.9.2/gems/little-plugger-1.1.2/lib/little-plugger.rb:270:inblock'
from /Library/Frameworks/MacRuby.framework/Versions/0.8/usr/lib/ruby/Gems/1.9.2/gems/little-plugger-1.1.2/lib/little-plugger.rb:268:in default_plugin_module:' from /Library/Frameworks/MacRuby.framework/Versions/0.8/usr/lib/ruby/Gems/1.9.2/gems/little-plugger-1.1.2/lib/little-plugger.rb:217:inplugin_module'
from /Library/Frameworks/MacRuby.framework/Versions/0.8/usr/lib/ruby/Gems/1.9.2/gems/little-plugger-1.1.2/lib/little-plugger.rb:156:in plugins' from /Library/Frameworks/MacRuby.framework/Versions/0.8/usr/lib/ruby/Gems/1.9.2/gems/little-plugger-1.1.2/lib/little-plugger.rb:176:ininitialize_plugins'
from /Library/Frameworks/MacRuby.framework/Versions/0.8/usr/lib/ruby/Gems/1.9.2/gems/bones-3.5.4/bin/bones:11:in <main>' from /usr/bin/bones:19:in

'

I am using latest nightly of MacRuby 0.8

Regards,
kam

Just when I decided to use Project Sprouts (http://projectsprouts.org/) to automate the generation of my projects (and this does not only include software projects), I've found out about Bones. Sprouts is great, but way too complex; Bones seems to be more agnostic and the code looks cleaner and simpler to extend (through the plugins). Looks awesome!

I've been using Chef for server provisioning and app deployment, and I think Bones bridges the gap of getting started with the app (including having the basis for Chef setup already).

I'll play with it and blog, let's see how it goes!

Cheers and thanks ;)

Marcelo.

I used bones 3.7.1 today to create a new skeleton. I have rspec 2.7.0 installed. After putting a few basic pieces together, I tried running "rake spec" but the task did nothing. Changing into the spec directory and running the spec directly printed all sorts of deprecation warnings about the syntax.

I checked the commits to bones. The latest ones bumped the rspec dependency for bones itself, but bones still creates skeleton files that only work with rspec 1.x.

I'm trying to upgrade a project to the latest Bones structure but rspec seems to not be supported. Has it been moved to a plugin? If so, how do I use plugins to add it back to my project?