Hi all Lift-developers,
I have noticed a few commits recently where the declarations for
specifications could be reduced to something simpler.
For example:
import org.specs._
import org.specs.runner._
class BindingsSpecTest extends Runner(BindingsSpec) with JUnit with
Console
object BindingsSpec extends Specification
can be written as
import org.specs._
class BindingsSpec extends SpecificationWithJUnit
- the BindingsSpec class will run with maven, provided that you add
the proper include directive in the pom.xml file, like this, for
example:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.4.3</version>
<configuration>
<useSystemClassLoader>false</useSystemClassLoader>
<argLine>-Xmx512m</argLine>
<forkMode>always</forkMode>
<includes>
<include>**/*Unit.java</include>
<include>**/*Spec.java</include>
</includes>
<excludes>
<exclude>**/*Test.java</exclude>
</excludes>
</configuration>
</plugin>
- It will also run in the console, like this:
scala -cp <classpath> run net.liftweb.http.BindingsSpec
I hope this helps, please ping me if you have any concern with this.
Eric.
PS: I forgot to mention that I am guilty of the situation above
because of how things were done in specs when I starting contributing
the first specifications to Lift,...
PPS: I've edited the User Guide to make clear what was the preferred
way of using JUnit with specs:
http://code.google.com/p/specs/wiki/RunningSpecs#Run_your_specification_with_JUnit4
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en.
