buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Donald (JIRA)" <j...@apache.org>
Subject [jira] Commented: (BUILDR-535) Failing "checks" produce no meaningful errors
Date Wed, 13 Oct 2010 13:16:32 GMT

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

Peter Donald commented on BUILDR-535:
-------------------------------------

I can reproduce it using jruby 1.52 + buildr 1.42 on both osx and windows. I will try to look
into it further but probably wont get a chance before this release.

> Failing "checks" produce no meaningful errors 
> ----------------------------------------------
>
>                 Key: BUILDR-535
>                 URL: https://issues.apache.org/jira/browse/BUILDR-535
>             Project: Buildr
>          Issue Type: Bug
>          Components: Test frameworks
>    Affects Versions: 1.4.2
>            Reporter: Peter Donald
>             Fix For: 1.4.3
>
>
> Adding checks to build are expected to cause the build to fail with a meaningful failure
reason. However it looks like the method "Object.error" is redefined somewhere and thus when
the check fails it results in an exception such as 
> "Buildr aborted!
> ArgumentError : wrong # of arguments(1 for 0)"
> An example build file exhibiting this failure:
> {code}
> define 'foo' do
>   project.version = '1.0'
>   project.group = 'foo'
>   package :jar
>   
>   check package(:jar), 'should fail' do
>     it.should contain('META-INF/MANIFEST.MF_not_exist')
>   end
> end
> {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