Features

Confluence 5

...

Greenpepper-wiki macro

With the new Rich text editor of confluence 5, creating specification table can be more time consuming than it was before. To help you keep your pace, we have introduced a new macro :

...

This macro will allow you to write your specification in wiki format.

includeStyle=true not working on output page

Greenpepper Core

...

Hidden stacktraces in the output pages

Image Removed

Greenpepper 4 will get you the following on the same page .
Image Added	Image Added
	If you want to see the stacktrace, you will need to click on the '+' and '-' sign.

Image Removed 

Maven Plugin

...

Single Specification testing

Bug Fixes

...

Maven Runner 

Supporting Maven 3 repositories

Although the embedded version of Maven is still Maven 2, the Runner is now compatible with Maven 3 local repositories.

Supporting classifier artifact

Greenpepper 4 Maven runner will now allow you to specify artifacts with classifier. In that case, only that artifact will be downloaded and added to the classpath.

This functionality is designed for project wanting to test on a single JAR, created for instance using the Maven Assembly Plugin, or Maven Shade Plugin. 

java -jar greenpepper-maven-runner-4.0-complete.jar -p com.github.strator-dev.greenpepper:greenpepper-client:jar:complete:4.0 MySpecification.html

Don't use my specification !

The GreenPepper Maven Runner could, in some cases, overwrite the input file with the output. Version 4.0 will now create a file with the same name as the input suffixed with '.out' .

➜  test git:(b8ee7c8) java -jar ../greenpepper-maven-runner-4.0-RC1-complete.jar -p com.github.strator-dev.greenpepper:greenpepper-client:jar:complete:4.0-RC1 MySpecification.html -v
➜  test git:(b8ee7c8) tree 
.
├── MySpecification.html
└── MySpecification.html.out

0 directories, 2 files