Yes, I have a JIRA in to turn that into an m2 plugin itself. Not sure that's exactly what you want, as it forks m2 to run the goals.
Really, an integration test should not be needed - if the plugin is in Java, you should be able to test with junit. At least up until the point that multiple goals need to occur inside the lifecycle. I think the best thing to do would be to put together the tests you need and single out the things you don't think are covered by juni, and we can all discuss what we can provide for plugin writers - whether it be a way to completely run m2, or a test suite that provides APIs to help test with junit, or testing implementations of some of the m2 components. Just to double check too - you're going to run your ideas for the plugin past here as well? I assume you are planning now, and using test first, so testing was the first thing :) Whether the clover plugin is written as part of the m2 project or not, the plugin API is currently being finalised and any reporting coming out of it should help form the m2 API's for that along with the other plugins getting developed, so I want to make sure everyone is helping each other out :) Thanks, Brett Vincent Massol wrote: >Hi, > >I'm writing a Clover plugin and I'd like to write tests for it as I >progress. Obviously most tests will have to be integration tests. > >I've seen that the m2 team has developed an integration test system in >maven-components/maven-core-it-verifier with tests in >maven-components/maven-core-it. > >I was wondering if this tester is made available in the form of a m2 plugin >for external plugin writers? > >Thanks >-Vincent > > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
