Installing the GreenPepper Maven Plugin

In order to install the GreenPepper Maven Plugin, it is necessary to add a plugin entry to your project's pom.xml.

<plugin>
	<groupId>com.greenpepper</groupId>
	<artifactId>greenpepper-maven-plugin</artifactId>
	<version>4.0.0-SNAPSHOT</version>
	...
	<!-- further configuration here -->
</plugin>

For automatic downloads and upgrades, it is possible to add additional repositories to your project's pom.xml like this:

<repositories>
	<repository>
		<id>novatec</id>
		<url>http://nexus.novatec-gmbh.lan/content/groups/public</url>
		<snapshots>
			<enabled>true</enabled>
			<updatePolicy>never</updatePolicy>
		</snapshots>
		<releases>
			<enabled>true</enabled>
			<updatePolicy>never</updatePolicy>
		</releases>
</repositories>
 
<pluginRepositories>
	<id>novatec</id>
	<url>http://nexus.novatec-gmbh.lan/content/groups/public</url>
	<snapshots>
		<enabled>true</enabled>
		<updatePolicy>never</updatePolicy>
	</snapshots>
	<releases>
		<enabled>true</enabled>
		<updatePolicy>never</updatePolicy>
	</releases>
</pluginRepositories>

Configuring the GreenPepper Maven Plugin

Considering the default Maven Build Lifecycle, there are three phases in which the GreenPepper Maven Plugin is used.
 

• During the Pre-Integration Test, the plugin is used to compile and copy to fixture classes of an application. By default, the compiled classes are copied to:
  ${project.build.directory}/fixture-test-classes/

• During the next phase, the Integration Test, the plugin is used to execute the specifications of an application. As the result of an execution, it generates reports in plain HTML file format which are by default stored in:
  ${basedir}/target/greenpepper-reports/

• Finally, during the Post-Integration Test, the plugin creates the fixture jars of an application. These are typically generated in:
  ${basedir}/target/