buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antoine Toulme (JIRA)" <j...@apache.org>
Subject [jira] Commented: (BUILDR-513) --trace no longer works as in 1.4.1
Date Tue, 21 Sep 2010 06:41:33 GMT

    [ https://issues.apache.org/jira/browse/BUILDR-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912859#action_12912859
] 

Antoine Toulme commented on BUILDR-513:
---------------------------------------

I'd be interested to see if you can reproduce this with some sample code. Please attach a
test case here, and we will integrate it to the integration testing suite.

> --trace no longer works as in 1.4.1
> -----------------------------------
>
>                 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
>             Fix For: 1.4.2
>
>
> 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.


Mime
View raw message