Plugin test harness

any clues on what you wanted here? is it covered by the integration testing?

I came to this topic looking for a way to test maven mojos. How are other people writing unit tests for their mojo code?

dave

I am Dave. Kenney Westerhof pointed me to the apache maven sandbox for an example test project runner maven-it-plugin used for integration tests:

https://svn.apache.org/repos/asf/maven/sandbox/plugins/

Still working on using it with the xmlbeans maven plugin.

Strangely, this issue doesn't have a priority (priority.none).

oh handy, went looking for a jira ticket on this and there it is all assigned to me and everything.

I think the plugin testing harness is moderately useful at this point with a couple of caveats...

I have/or will be soon commiting something that will break it from building against 2.1-SNAPSHOT. That is because to get the StubMavenProject to be instantiated and populated we need an empty constructor on the MavenProject instance I am extending. I have the local change on that but will talk to brett or jason about getting that worked out when I see then again.

On this issue I will also attach the working example of the maven-compiler-plugin where you can see it in action. I'll also attach the simple case for the maven-jar-plugin since that shows how to fill out the maven project stub

I should also say the maven project stub is really dumb at this point and as functionality is needed on it we can implement that as we go.

mojo/mojo-sandbox/maven-plugin-testing/maven-plugin-testing-harness

that is the location of the actual plugin...

I'll write up a confluence page on how to use it more and some things to consider and post the url here later

http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Harness

I was able to get the maven-site-plugin instantiated by adding the plugin harness test dependency and update the maven -site-plugin pom reference to maven-artifact.

IMO that is going to be the biggest limiting factor to this approach, reconsiling the version of dependencies. I have added a mess of dependencies to the plugin-testing-harness pom but they are not used if the project in question has a different version of the dependency, like with the site plugin.

At this point I think we are left with individual details for the framework on a per plugin basis. I implemented most of the maven project stub this morning so it is mostly useful, missing some things but for basic usage should be in decent shape.

fyi:

this will not compile util we get the MavenProject class to have an empty constructor, I had arranged to have that taken care of but it doesn't look like it has been yet so that is a bit of a hurdle to using this

I'll include that patch to this issue and hopefully a kind individual can apply it to the trunk

imported to sandbox