You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Peter Donald (JIRA)" <ji...@apache.org> on 2011/06/22 12:11:25 UTC
[jira] [Closed] (BUILDR-65) EasyB test files present in project are
causing a "No file or directory" error
[ https://issues.apache.org/jira/browse/BUILDR-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Donald closed BUILDR-65.
------------------------------
> EasyB test files present in project are causing a "No file or directory" error
> ------------------------------------------------------------------------------
>
> Key: BUILDR-65
> URL: https://issues.apache.org/jira/browse/BUILDR-65
> Project: Buildr
> Issue Type: Bug
> Components: Test frameworks
> Affects Versions: 1.3
> Environment: os x
> Reporter: Nicolas Modrzyk
> Assignee: Victor Hugo Borja
>
> I am building tempo: tempo.iintalio.org/tempo/trunk, and more precisely the tms-service subproject.
> I have easyb groovy files in the project:
> ls src/test/stories
> returns
> taskPersistenceBehavior.groovy
> and when running buildr install I get:
> IOException: No file or directory with the name /Users/niko/projects/tempo/tms-service/target/resources
> ** Invoke tempo:tms-service:test:teardown (first_time)
> ** Execute tempo:tms-service:test:teardown
> rake aborted!
> No file or directory with the name /Users/niko/projects/tempo/tms-service/target/resources
> /Users/niko/tools/gemrepository/gems/buildr-1.3.0/lib/buildr/java/test_frameworks.rb:58:in `new'
> /Users/niko/tools/gemrepository/gems/buildr-1.3.0/lib/buildr/java/test_frameworks.rb:58:in `filter_classes'
> /Users/niko/tools/gemrepository/gems/buildr-1.3.0/lib/buildr/java/test_frameworks.rb:180:in `tests'
> /Users/niko/tools/gemrepository/gems/buildr-1.3.0/lib/buildr/core/test.rb:423:in `run_tests'
> /Users/niko/tools/gemrepository/gems/buildr-1.3.0/lib/buildr/core/test.rb:196:in `initialize'
> It all works fine if I create the missing folder (target/resources)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira