> -----Original Message----- > From: John Casey [mailto:[EMAIL PROTECTED] > Sent: lundi 19 décembre 2005 18:11 > To: Maven Developers List > Subject: Re: Integration tests for core plugins > > Hi Vincent, > > IMO, we should be using the IT plugin, since we're testing a given > plugin in the context of a running Maven instance, not on its own. For > tests we *can* do in isolation, I think unit testing still needs to be > part of the solution, maybe even using PlexusTestCase derivatives where > they're needed. There has been some talk about creating a test harness > that would essentially mock up the context maven instance, but IMO this > is dangerous, since it will mean maintaining and resyncing an extra > codebase simply to support testing.
I agree. > I spent some time on Saturday night getting the it plugin up and running > again, and I think it's time to release it. I'll call a vote for it, and > see if I can get it released at the end of the week or something, That'd be cool. > but > I'm going to be on vacation...so things could be a bit sketchy. I think > it's ready to release the first version and move it out of the sandbox. > It could use some documentation, but it seems to work pretty well. Some alpha would do just nice for now I think. > As for the 403 error on the plugin-parent's sha1 file, I've fixed the > permissions on both the staging repository and ibiblio. I'm not sure > what caused this, but it may be related to a bug that Brett's been > seeing when doing scp deployments (he released the plugin parent, IIRC). > There's an issue open for it...it was marked as blocker priority at one > point, but I'm not sure whether it still is. Thanks a lot. It works fine now. -Vincent > Vincent Massol wrote: > > Hi, > > > > I'm working again on the clover plugin (which I'd like to release ASAP). > I > > wanted to move the it test I have in components/examples to the plugin > > itself. > > > > I wanted to use the it plugin for running it but I've just realized that > the > > it plugin has never been released (not even in alpha). Thus if I use it, > I > > guess Continuum will fail. > > > > I checked a few plugins and I couldn't see any integration tests for > them so > > I'm wondering what's our strategy WRT it tests for our core plugins. > > > > Should we use the it plugin? > > Should we use directly the embedder in our tests? > > > > I think it makes more sense to use the it plugin. In that case could we > > release an alpha version of it? > > > > On a releated note, I've moved to Maven 2.0.1 final and I've tried to > build > > the it plugin from sources. It's failing with: > > > > Caused by: java.io.IOException: Server returned HTTP response code: 403 > for > > URL: > > http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven-plugin- > parent/2 > > .0.1/maven-plugin-parent-2.0.1.pom.sha1 > > > > Any idea? > > > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
