> -----Original Message-----
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mercredi 11 mai 2005 07:04
> To: Maven Users List
> Subject: Re: Clover Plugin 1.7 and multiproject on Maven 1.0.2
> 
> This looks like a much better solution to me, and could make for a
> clover:multiproject goal (replace the drools include with a loop over
> reactorProjects).
> 
> Vincent, WDYT?

Done with lots of other changes. I'm sending another email about them.

Thanks
-Vincent

> 
> - Brett
> 
> On 5/11/05, Mark Proctor <[EMAIL PROTECTED]> wrote:
> > I gave up on the shared db after a while, had someone else look at it
> > and they couldn't figure out why it wasn't working. Did some research
> > found the clover:merge option and that works really nicely, better still
> > I dont have to do any clover db path hacking, I can just accept all
> > defaults:
> >
> >     <goal name="drools:clover" prereqs="clean-all:prepare">
> >       <!-- generate clover dbs for each sub project -->
> >       <j:set var="goal" value="drools:clover" />
> >       <attainGoal name="multiproject:goal"/>
> >
> >       <attainGoal name="clover:on"/>
> >
> >       <!-- can't get shared db to work, so use merge functionality -->
> >       <attainGoal name="clover:merge" />
> >
> >       <attainGoal name="clover:report"/>
> >
> >     </goal>
> >
> >     <goal name="clover:merge" prereqs="clover:init">
> >        <clover-merge initString="${maven.clover.database}">
> >           <cloverDbSet dir=".">
> >             <include name="drools-
> */target/clover/database/clover_coverage.db"/>
> >           </cloverDbSet>
> >        </clover-merge>
> >     </goal>
> >
> >
> > Mark Proctor wrote:
> >
> > > yes thought I read that in the plugin.jelly, I'm going to try 1.6 with
> > > the license for 1.7 - see if that helps.
> > >
> > > Mark
> > > Vincent Massol wrote:
> > >
> > >>
> > >>
> > >>> -----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]
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > 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]

Reply via email to