...
In step one ("Installing the GreenPepper Maven Plugin") we had a look on a short block of code where it said "further configuration here". Below you find an example of how said configuration could look like.
| Code Block | ||
|---|---|---|
| ||
<plugin>
<groupId>com.greenpepper</groupId>
<artifactId>greenpepper-maven-plugin</artifactId>
<version><!-- your version of the GreenPepper Maven Plugin --></version>
<configuration>
<source><!-- your source version --></source>
<target><!-- your target version --></target>
<fixtureSourceDirectory><!-- source directory of your fixtures, for example: src/fixture/java --></fixtureSourceDirectory>
<fixtureOutputDirectory><!-- output directory of the compiled fixture classes, for example: target/fixture-test-classes --></fixtureOutputDirectory>
<specsDirectory><!-- destination for downloaded specification files, for example: src/sprecs--></specsDirectory>
<reportsDirectory><!-- destination for generated HTML reports, for example: target/greenpepper-reports</reportsDirectory>
<reportsType><!-- the file format of your reports (XML or HTML) --></reportsType>
<resources>
<resource>
<directory><! -- directory for a specific resource. Example: src/fixture/resources--></directory>
<excludes>
<exclude>**/*.java</exclude>
</excludes>
</resource>
</resources>
<repositories>
<repository>
<type><!-- fully qualified name of your suit resolver class, for instance: com.greenpepper.repository.FileSystemRepository --></type>
<root><!-- root directory of the current repository. Example: ${basedir}/src/fixture/specs --></root>
<suites>
<suite><!-- the suit's URI --></suite>
</suites>
</repository>
<repository>
<type><!-- fully qualified name of your test resolver. --></type>
<tests>
<test><!-- the test's URI --></test>
</tests>
</repository>
</repositories>
</configuration>
<plugin> |
...