[
https://issues.apache.org/jira/browse/BUILDR-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920524#action_12920524
]
Alex Boisvert commented on BUILDR-535:
--------------------------------------
I can't reproduce on my system :(
boisv...@smudge:~/tmp/buildr-check$ /usr/bin/buildr _1.4.2_ package
(in /home/boisvert/tmp/buildr-check, development)
Building foo
Packaging foo
Packaging foo-1.0.jar
/home/boisvert/tmp/buildr-check/buildfile:7
/home/boisvert/tmp/buildr-check/target/foo-1.0.jar should fail
Expected /home/boisvert/tmp/buildr-check/target/foo-1.0.jar to contain
'META-INF/MANIFEST.MF_not_exist'
Buildr aborted!
RuntimeError : Checks failed for project foo (see errors above).
(See full trace by running task with --trace)
> 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.
