[ http://jira.codehaus.org/browse/MNG-32?page=comments#action_60913 ]
Jesse McConnell commented on MNG-32: ------------------------------------ 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. > 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 > Attachments: maven-compiler-plugin.jar, maven-jar-plugin.jar > > -- 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
