> -----Original Message----- > From: Mark Proctor [mailto:[EMAIL PROTECTED] > Sent: mardi 10 mai 2005 21:18 > To: Maven Users List > Subject: Re: Clover Plugin 1.7 and multiproject on Maven 1.0.2 > > I upgraded because the license ran out, no we dont fork the tests (apart > from python) - but that wasn't needed before.
Hmm... forget that, I had forgotten that I'm forcing a fork in the Clover plugin... so yes, you're forking the tests but you don't know it... ;-) -Vincent > > Mark > Vincent Massol wrote: > > >Hi Mark, > > > > > > > >>-----Original Message----- > >>From: Mark Proctor [mailto:[EMAIL PROTECTED] > >>Sent: mardi 10 mai 2005 06:15 > >>To: Maven Users List > >>Subject: Re: Clover Plugin 1.7 and multiproject on Maven 1.0.2 > >> > >> > > > >[snip] > > > > > > > >>>>I'm trying to do clover multiproject build with maven 1.0.2 and clover > >>>>plugin 1.7. This use to work but with the upgrade to 1.7 I noticed it > >>>> > >>>> > >>is > >> > >> > >>>>now broken, not sure if its 1.7 or a change in our code. > >>>> > >>>> > > > >Why don't you try with the previous version you were using the check if > it's > >in the clover plugin or not? > > > >One point though: Are you forking your tests or not? > > > >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]
