You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Daniel Spiewak (JIRA)" <ji...@apache.org> on 2009/06/15 20:22:07 UTC
[jira] Created: (BUILDR-286) Specs Runner Fails on Indistinct
Companion Object
Specs Runner Fails on Indistinct Companion Object
-------------------------------------------------
Key: BUILDR-286
URL: https://issues.apache.org/jira/browse/BUILDR-286
Project: Buildr
Issue Type: Bug
Components: Test frameworks
Affects Versions: 1.3.4
Environment: JRuby 1.3.1, Mac OS X, SoyLatte 1.6.0_03-p3
Reporter: Daniel Spiewak
Assignee: Daniel Spiewak
Priority: Critical
Fix For: 1.3.5
The Specs auto-detection seems to do something unfortunate whenever the specification object is accompanied by a companion class. The most common case for this is when a Specs runner class accompanies the specification (for tools like Eclipse's JUnit View). For example:
import org.specs._
import runner.JUnit4
object MySpecs extends Specification {
...
}
class MySpecs extends JUnit4(MySpec)
When running `buildr` with this source in the src/spec/scala/ directory, the following error is produced:
Running java MySpecs
Exception in thread "main" java.lang.NoSuchMethodError: main
The following tests failed:
MySpecs
Buildr aborted!
Tests failed!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (BUILDR-286) Specs Runner Fails on Indistinct
Companion Object
Posted by "Daniel Spiewak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Spiewak resolved BUILDR-286.
-----------------------------------
Resolution: Fixed
Fixed in r784956.
> Specs Runner Fails on Indistinct Companion Object
> -------------------------------------------------
>
> Key: BUILDR-286
> URL: https://issues.apache.org/jira/browse/BUILDR-286
> Project: Buildr
> Issue Type: Bug
> Components: Test frameworks
> Affects Versions: 1.3.4
> Environment: JRuby 1.3.1, Mac OS X, SoyLatte 1.6.0_03-p3
> Reporter: Daniel Spiewak
> Assignee: Daniel Spiewak
> Priority: Critical
> Fix For: 1.3.5
>
>
> The Specs auto-detection seems to do something unfortunate whenever the specification object is accompanied by a companion class. The most common case for this is when a Specs runner class accompanies the specification (for tools like Eclipse's JUnit View). For example:
> import org.specs._
> import runner.JUnit4
> object MySpecs extends Specification {
> ...
> }
> class MySpecs extends JUnit4(MySpec)
> When running `buildr` with this source in the src/spec/scala/ directory, the following error is produced:
> Running java MySpecs
> Exception in thread "main" java.lang.NoSuchMethodError: main
> The following tests failed:
> MySpecs
> Buildr aborted!
> Tests failed!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.