Maybe if the test-harness can be provided with a pom.xml file and from
there it can build several of the needed expressions. Of course, the
plugin configuration should already be in the pom so we need not provide
two separate files for the test-harness. I'd also suggest parsing
${basedir} t
Jesse McConnell wrote:
org.apache.maven.shared
maven-plugin-testing-harness
1.0-beta-1
test
http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Harness
I originally put this harness together with help from jason so that we
could instantiate mojo's easily in test cases and
org.apache.maven.shared
maven-plugin-testing-harness
1.0-beta-1
test
http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Harness
I originally put this harness together with help from jason so that we
could instantiate mojo's easily in test cases and feed in
configuration se
