You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2010/09/21 15:23:32 UTC
[jira] Resolved: (BUILDR-513) --trace fails with NoMethodError :
undefined method `include?' for nil:NilClass
[ https://issues.apache.org/jira/browse/BUILDR-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert resolved BUILDR-513.
----------------------------------
Assignee: Alex Boisvert
Resolution: Fixed
<sigh> I should have caught this before 1.4.2 release.
Workaround to avoid the failure is to write: --trace=
Fixed and added specs.
Sending CHANGELOG
Sending lib/buildr/core/application.rb
Sending spec/core/application_spec.rb
Transmitting file data ...
Committed revision 999399.
> --trace fails with NoMethodError : undefined method `include?' for nil:NilClass
> -------------------------------------------------------------------------------
>
> Key: BUILDR-513
> URL: https://issues.apache.org/jira/browse/BUILDR-513
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.4.2
> Reporter: Peter Donald
> Assignee: Alex Boisvert
> Fix For: 1.4.3
>
>
> In the past you could invoke buildr via something like "buildr package --trace" but now this fails with
> {code}
> Buildr aborted!
> NoMethodError : undefined method `include?' for nil:NilClass
> C:/Applications/jruby-1.5.1/lib/ruby/gems/1.8/gems/buildr-1.4.2-java/lib/buildr/core/application.rb:352:in `standard_buildr_options'
> C:/Applications/jruby-1.5.1/lib/ruby/1.8/optparse.rb:1268:in `call'
> C:/Applications/jruby-1.5.1/lib/ruby/1.8/optparse.rb:1268:in `parse_in_order'
> C:/Applications/jruby-1.5.1/lib/ruby/1.8/optparse.rb:1255:in `catch'
> C:/Applications/jruby-1.5.1/lib/ruby/1.8/optparse.rb:1255:in `parse_in_order'
> C:/Applications/jruby-1.5.1/lib/ruby/1.8/optparse.rb:1249:in `order!'
> C:/Applications/jruby-1.5.1/lib/ruby/1.8/optparse.rb:1340:in `permute!'
> C:/Applications/jruby-1.5.1/lib/ruby/1.8/optparse.rb:1361:in `parse!'
> C:/Applications/jruby-1.5.1/lib/ruby/gems/1.8/gems/buildr-1.4.2-java/lib/buildr/core/application.rb:254:in `handle_options'
> C:/Applications/jruby-1.5.1/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2009:in `init'
> C:/Applications/jruby-1.5.1/lib/ruby/gems/1.8/gems/buildr-1.4.2-java/lib/buildr/core/application.rb:518:in `standard_exception_handling'
> C:/Applications/jruby-1.5.1/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2007:in `init'
> C:/Applications/jruby-1.5.1/lib/ruby/gems/1.8/gems/buildr-1.4.2-java/lib/buildr/core/application.rb:136:in `run'
> C:/Applications/jruby-1.5.1/lib/ruby/gems/1.8/gems/buildr-1.4.2-java/lib/buildr/core/application.rb:518:in `standard_exception_handling'
> C:/Applications/jruby-1.5.1/lib/ruby/gems/1.8/gems/buildr-1.4.2-java/lib/buildr/core/application.rb:135:in `run'
> C:/Applications/jruby-1.5.1/lib/ruby/gems/1.8/gems/buildr-1.4.2-java/bin/buildr:19
> C:/Applications/jruby-1.5.1/lib/ruby/gems/1.8/gems/buildr-1.4.2-java/bin/buildr:19:in `load'
> C:/Applications/jruby-1.5.1/bin/buildr:19
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.