buildr-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niklaus Giger <niklaus.gi...@member.fsf.org>
Subject Re: Questions on howto build a new Buildr plugin
Date Tue, 17 Apr 2012 19:54:24 GMT
Hi

Thanks everybody for the feedback. I think I can live with braid, but it just 
never occured to me that you were using it. (I did not yet use git submodules 
a lot.) But I have the following questions:

a) Why don't you include the .braids file in the plugin. If it had been there, 
I might have stumbled about it a lot earlier.

b) I was able to setup a skeleton (nothing working yet) under 
https://github.com/ngiger/buildrizpack by copying the rakelib directory from 
buildr and adapting it to buildrizpack.

The rake tasks 'gem', 'install', 'rdoc' work. The only other target I really 
am interested in is 'spec'. But it fails with the following error msg

> /home/niklaus/.rvm/rubies/ruby-1.9.2-p318/bin/ruby -S bundle exec rspec
> --format html --out _reports/specs.html --backtrace
> spec/buildrizpack/package_spec.rb
> /opt/src/buildrizpack/spec/spec_helpers.rb:22:in `block in included':
> undefined method `version_requirements' for
> #<Gem::Dependency:0x00000003ca5960> (NoMethodError)
> 
>         from /opt/src/buildrizpack/spec/spec_helpers.rb:22:in `each'
>         from /opt/src/buildrizpack/spec/spec_helpers.rb:22:in `included'
>         from /opt/src/buildrizpack/buildr/spec/spec_helpers.rb:53:in
>         `include' from
>         /opt/src/buildrizpack/buildr/spec/spec_helpers.rb:53:in `<top
>         (required)>' from /opt/src/buildrizpack/spec/spec_helpers.rb:29:in
>         `require' from /opt/src/buildrizpack/spec/spec_helpers.rb:29:in
>         `<top (required)>' from
>         /opt/src/buildrizpack/spec/buildrizpack/package_spec.rb:16:in
>         `require' from
>         /opt/src/buildrizpack/spec/buildrizpack/package_spec.rb:16:in
>         `<top (required)>' from
>         /home/niklaus/.rvm/gems/ruby-1.9.2-p318@buildr/gems/rspec-core-2.1
>         .0/lib/rspec/core/configuration.rb:334:in `load' from
>         /home/niklaus/.rvm/gems/ruby-1.9.2-p318@buildr/gems/rspec-core-2.1
>         .0/lib/rspec/core/configuration.rb:334:in `block in
>         load_spec_files' from
>         /home/niklaus/.rvm/gems/ruby-1.9.2-p318@buildr/gems/rspec-core-2.1
>         .0/lib/rspec/core/configuration.rb:334:in `map' from
>         /home/niklaus/.rvm/gems/ruby-1.9.2-p318@buildr/gems/rspec-core-2.1
>         .0/lib/rspec/core/configuration.rb:334:in `load_spec_files' from
>         /home/niklaus/.rvm/gems/ruby-1.9.2-p318@buildr/gems/rspec-core-2.1
>         .0/lib/rspec/core/command_line.rb:18:in `run' from
>         /home/niklaus/.rvm/gems/ruby-1.9.2-p318@buildr/gems/rspec-core-2.1
>         .0/lib/rspec/core/runner.rb:55:in `run_in_process' from
>         /home/niklaus/.rvm/gems/ruby-1.9.2-p318@buildr/gems/rspec-core-2.1
>         .0/lib/rspec/core/runner.rb:46:in `run' from
>         /home/niklaus/.rvm/gems/ruby-1.9.2-p318@buildr/gems/rspec-core-2.1
>         .0/lib/rspec/core/runner.rb:10:in `block in autorun'
> 
> rake aborted!
> ruby -S bundle exec rspec --format html --out _reports/specs.html
> --backtrace spec/buildrizpack/package_spec.rb failed
> 
I tried to find a solution but got stucked after a while. Anybody knows about 
this problem?

<..<
> I already created a plugin to do makensis installers if you're into that:
> https://github.com/intalio/package_as_exe
I know, but I don't want to force another installer to my project, because 
using buildr will be a little intrusive, even if I will try to minimize the 
impact.


> 
> 
> 
> Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> 
> On Tuesday, April 17, 2012 at 5:59 AM, Alex Boisvert wrote:
> > On Mon, Apr 16, 2012 at 5:37 PM, Peter Donald <peter@realityforge.org 
(mailto:peter@realityforge.org)>wrote:
> > > I would maybe both of them as options and outline the various
> > > strengths/weaknesses of both approaches. I would still tend to use
> > > braid but each to their own ;)
> > 
> > Same position here.
> > 
> > alex

Best regards

-- 
Niklaus Giger

Mime
View raw message