Just realized I was missing a META-INF/plexus/components.xml file. Will try
with one.

-Vincent

> -----Original Message-----
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: dimanche 26 juin 2005 11:18
> To: 'Maven Developers List'
> Subject: RE: [m2] Forking a custom lifecycle in a report plugin?
> 
> Hi Jason,
> 
> I've uploaded it there:
> http://www.apache.org/~vmassol/maven-clover-plugin-20050626.zip
> 
> Thanks
> -Vincent
> 
> > -----Original Message-----
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Sent: dimanche 26 juin 2005 01:25
> > To: Maven Developers List
> > Subject: Re: [m2] Forking a custom lifecycle in a report plugin?
> >
> > On Sat, 2005-06-25 at 22:43 +0200, Vincent Massol wrote:
> > > Hi,
> > >
> > > I'm now trying to implement a Clover report mojo. I have:
> > >
> > > /**
> > >  * @goal report
> > >  * @execute phase="test" lifecycle="clover"
> > >  * @description Generate a Clover report
> > >  *
> > >  * @author <a href="mailto:[EMAIL PROTECTED]">Vincent Massol</a>
> > >  * @version $Id: $
> > >  */
> > > public class CloverReportMojo extends AbstractMavenReport
> > > [...]
> > >
> > > However when I type "m2 site:site" the custom clover lifecycle is not
> > > spawned. Is this working for report mojos?
> >
> > Can you post a tarball of the plug-in?
> >
> > You can also take a look at the maven-core-it-plugin which is test in
> > integration test it0027.
> >
> > --
> > jvz.
> >
> > Jason van Zyl
> > jason at maven.org
> > http://maven.apache.org
> >
> > happiness is like a butterfly: the more you chase it, the more it will
> > elude you, but if you turn your attention to other things, it will come
> > and sit softly on your shoulder ...
> >
> >  -- Thoreau
> >
> >
> > ---------------------------------------------------------------------
> > 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