scala spec & eclipse plug-in

ricky@ricky-desktop:~$ scala -classpath /home/ricky/specs/target/classes/
Welcome to Scala version 2.8.0.r17003-b20090130095225 (Java HotSpot(TM) Client VM, Java 1.6.0_11).
Type in expressions to have them evaluated.
Type :help for more information.

scala> object Tests extends org.specs.Specification { "oh my word" should { "not be censored" in { "oh my word it's.. like, oh my god".replaceAll("oh my god", "** ** ***") } } }
defined module Tests

scala> Tests.main(null)
Specification "Tests"
  oh my word should
  + not be censored

Total for specification "Tests":
Finished in 0 second, 137 ms
1 example, 0 expectation, 0 failure, 0 error

ricky@ricky-desktop:~$ scala -classpath /home/ricky/specs/target/classes/
Welcome to Scala version 2.8.0.r17003-b20090130095225 (Java HotSpot(TM) Client VM, Java 1.6.0_11).
Type in expressions to have them evaluated.
Type :help for more information.

scala> object Tests extends org.specs.Specification { "oh my word (which is not blasphemous)" should { "not be censored" in { "oh my word it's.. like, oh my god".replaceAll("oh my god", "** ** ***") } } }
defined module Tests

scala> Tests.main(null)
Specification "Tests"
  oh my word (which is not blasphemous) should
  + not be censored

Total for specification "Tests":
Finished in 0 second, 98 ms
1 example, 0 expectation, 0 failure, 0 error

Lord only knows (or should that be **** only knows?) why Specification's main exits the JVM at the end.

2009/2/2 Normen Müller <normen.mueller@googlemail.com>

He,

don't know where to file this issue.  Is that a eclipse plug-in or a scala spec bug:

What steps will reproduce the problem?
1. set up a simple specification with parentheses "()" in the description, e.g. "A list (a, b)" should {...}
2. run JUnit

What is the expected output?
A list (a, b) should

 What do you see instead?
/a tree node w/o any description/

What version of the product are you using?
latest

On what operating system?
osx

Cheers,
--
Normen Müller

So you are trying to tell me it's a eclipse plug-in bug, right? ;-)

On Feb 2, 2009, at 12:14 PM, Ricky Clarkson wrote:

> ricky@ricky-desktop:~$ scala -classpath /home/ricky/specs/target/
> classes/
> Welcome to Scala version 2.8.0.r17003-b20090130095225 (Java
> HotSpot(TM) Client VM, Java 1.6.0_11).
> Type in expressions to have them evaluated.
> Type :help for more information.
>
> scala> object Tests extends org.specs.Specification { "oh my word"
> should { "not be censored" in { "oh my word it's.. like, oh my
> god".replaceAll("oh my god", "** ** ***") } } }
> defined module Tests
>
> scala> Tests.main(null)
> Specification "Tests"
> oh my word should
> + not be censored
>
> Total for specification "Tests":
> Finished in 0 second, 137 ms
> 1 example, 0 expectation, 0 failure, 0 error
>
> ricky@ricky-desktop:~$ scala -classpath /home/ricky/specs/target/
> classes/
> Welcome to Scala version 2.8.0.r17003-b20090130095225 (Java
> HotSpot(TM) Client VM, Java 1.6.0_11).
> Type in expressions to have them evaluated.
> Type :help for more information.
>
> scala> object Tests extends org.specs.Specification { "oh my word
> (which is not blasphemous)" should { "not be censored" in { "oh my
> word it's.. like, oh my god".replaceAll("oh my god", "** **
> ***") } } }
> defined module Tests
>
> scala> Tests.main(null)
> Specification "Tests"
> oh my word (which is not blasphemous) should
> + not be censored
>
> Total for specification "Tests":
> Finished in 0 second, 98 ms
> 1 example, 0 expectation, 0 failure, 0 error
>
> Lord only knows (or should that be **** only knows?) why
> Specification's main exits the JVM at the end.
>
> 2009/2/2 Normen Müller
> He,
>
> don't know where to file this issue. Is that a eclipse plug-in or a
> scala spec bug:
>
> What steps will reproduce the problem?
> 1. set up a simple specification with parentheses "()" in the
> description, e.g. "A list (a, b)" should {...}
> 2. run JUnit
>
> What is the expected output?
> A list (a, b) should
>
> What do you see instead?
> /a tree node w/o any description/
>
> What version of the product are you using?
> latest
>
> On what operating system?
> osx
>
> Cheers,
> --
> Normen Müller
>
>
>
>

Cheers,
--
Normen Müller

It's not definitely one, but I only normally use Specs via the maven plugin, and I didn't want to introduce that to the problem space.  It could be that when used via main it does different things to when not.

2009/2/2 Normen Müller <normen.mueller@googlemail.com>

So you are trying to tell me it's a eclipse plug-in bug, right? ;-)

On Feb 2, 2009, at 12:14 PM, Ricky Clarkson wrote:

ricky@ricky-desktop:~$ scala -classpath /home/ricky/specs/target/classes/
Welcome to Scala version 2.8.0.r17003-b20090130095225 (Java HotSpot(TM) Client VM, Java 1.6.0_11).
Type in expressions to have them evaluated.
Type :help for more information.

scala> object Tests extends org.specs.Specification { "oh my word" should { "not be censored" in { "oh my word it's.. like, oh my god".replaceAll("oh my god", "** ** ***") } } }
defined module Tests

scala> Tests.main(null)
Specification "Tests"
 oh my word should
 + not be censored

Total for specification "Tests":
Finished in 0 second, 137 ms
1 example, 0 expectation, 0 failure, 0 error

ricky@ricky-desktop:~$ scala -classpath /home/ricky/specs/target/classes/
Welcome to Scala version 2.8.0.r17003-b20090130095225 (Java HotSpot(TM) Client VM, Java 1.6.0_11).
Type in expressions to have them evaluated.
Type :help for more information.

scala> object Tests extends org.specs.Specification { "oh my word (which is not blasphemous)" should { "not be censored" in { "oh my word it's.. like, oh my god".replaceAll("oh my god", "** ** ***") } } }
defined module Tests

scala> Tests.main(null)
Specification "Tests"
 oh my word (which is not blasphemous) should
 + not be censored

Total for specification "Tests":
Finished in 0 second, 98 ms
1 example, 0 expectation, 0 failure, 0 error

Lord only knows (or should that be **** only knows?) why Specification's main exits the JVM at the end.

2009/2/2 Normen Müller <normen.mueller@googlemail.com>
He,

don't know where to file this issue.  Is that a eclipse plug-in or a scala spec bug:

What steps will reproduce the problem?
1. set up a simple specification with parentheses "()" in the description, e.g. "A list (a, b)" should {...}
2. run JUnit

What is the expected output?
A list (a, b) should

 What do you see instead?
/a tree node w/o any description/

What version of the product are you using?
latest

On what operating system?
osx

Cheers,
--
Normen Müller

Cheers,
--
Normen Müller