[ http://jira.codehaus.org/browse/MNG-32?page=comments#action_60695 ]
Jesse McConnell commented on MNG-32: ------------------------------------ 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. > Plugin test harness > ------------------- > > Key: MNG-32 > URL: http://jira.codehaus.org/browse/MNG-32 > Project: Maven 2 > Type: Task > Components: Sandbox, Plugin API, Design, Patterns & Best Practices > Reporter: Jason van Zyl > Assignee: Jesse McConnell > Priority: Blocker > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
