The project contains simple test utils for JUnit and DBUnit. See documentation for more Details.
Repository needed in your project's pom.xml :
<repository>
<id>sb-utils-bintray</id>
<name>Seitenbau utils bintrayrepository</name>
<url>http://dl.bintray.com/seitenbau/utils</url>
</repository>
Dependencies needed in your project's pom.xml :
<dependency>
<groupId>com.seitenbau.stu</groupId>
<artifactId>stu-common</artifactId>
<version>0.2.1-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>com.seitenbau.stu</groupId>
<artifactId>stu-database</artifactId>
<version>0.2.1-SNAPSHOT</version>
</dependency>
apply plugin: 'java'
repositories {
mavenCentral()
maven { url "http://dl.bintray.com/seitenbau/utils" }
mavenLocal()
}
dependencies {
compile("com.seitenbau.stu:stu-common:0.2.1-SNAPSHOT")
compile("com.seitenbau.stu:stu-database:0.2.1-SNAPSHOT")
}
Use provided gradlew installed. STU currently only compiles with a JDK 1.8.
gradlew build
Used with mavenLocal() (typically at $USER_HOME/.m2/repository).
gradlew install
To generate the documentation please invoke:
gradlew asciidoctor
The documentation is generated to stu/documentation/html/stu.html.
To import the project into eclipse invoke:
gradlew eclipse
Then the project can be imported as eclipse projects. Please be sure to use the code-conventions-sb-testing.xml file from src/eclipse folder.
To import the project into IntelliJ IDEA invoke:
gradlew idea
Then the project can be open in IntelliJ.When you use IntelliJ version > 12, IntelliJ has build in gradle support then the project can direct be opened. When the workspace is ready the gradle task generateDataSetDsl should be invoked.
The documentation can be found here. The asciidoc files are stored in the subproject stu-documentation.