You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Nicolas Modrzyk (JIRA)" <ji...@apache.org> on 2008/05/03 01:10:56 UTC
[jira] Created: (BUILDR-65) EasyB test files present in project are
causing a "No file or directory" error
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
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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-65) EasyB test files present in project
are causing a "No file or directory" error
Posted by "Victor Hugo Borja (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596619#action_12596619 ]
Victor Hugo Borja commented on BUILDR-65:
-----------------------------------------
Looking at the stacktrace it seems like the test framework for your project is junit and not easyb.
To select easyb use:
test.using :easyb
Also, the sandard directory for groovy specs is "src/spec/groovy", of course you can customize this to fit your current layout by using layouts:
my_layout = Layout.new
my_layout[:source, :spec, :groovy] = 'src/test/stories'
define 'foo', :layout=>my_layout do
test.using :easyb
end
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (BUILDR-65) EasyB test files present in project
are causing a "No file or directory" error
Posted by "Victor Hugo Borja (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Victor Hugo Borja reassigned BUILDR-65:
---------------------------------------
Assignee: Victor Hugo Borja
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (BUILDR-65) EasyB test files present in project
are causing a "No file or directory" error
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Assaf Arkin resolved BUILDR-65.
-------------------------------
Resolution: Fixed
Assuming from the comment this issue is closed.
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-65) EasyB test files present in project
are causing a "No file or directory" error
Posted by "Nicolas Modrzyk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597772#action_12597772 ]
Nicolas Modrzyk commented on BUILDR-65:
---------------------------------------
Thanks !
I have actually both junit and easyb in the same project.
I also did fix the layout when running my tests, (not committed since I could not integrate with buildr 1.3)
> 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.
-
You can reply to this email to add a comment to the issue online.