Unit tests are not truly testing configuration via a pom file

[dgrierso]

The configuration in the mojos within the unit tests is presently done via the setters to configure the @parameters applied to the mojo.

However, this does not allow us to unit test the default behaviour of the @parameters - for example the use of default-value or @required to ensure the behaviour of the plugin is correct when these items are omitted.

[dgrierso]

A better way to do this would be to do something similar to that done within the maven-ant-plugin by creating an individual unit test pom.xml for each area of functionality we want to test.

We would invoking the unit test using the appropriate file.