The wiki page has been part of the web site for some time now.

See http://maven.apache.org/reference/developers/developer-guide.html
--
dIon Gillard, Multitask Consulting
Blog:      http://blogs.codehaus.org/people/dion/



Trygve Laugstøl <[EMAIL PROTECTED]> wrote on 18/12/2003 
08:14:25 AM:

> There is a wiki page on how to write a simple plugin:
> 
>   http://wiki.codehaus.org/maven/HowToCreateYourFirstPlugIn2
> 
> It doesnt include any info on how to implement it though. Feel free to 
add
> it to the wiki if you really find it usefull.
> 
> The best reference for creating plugins is still all the existing 
plugins,
> several which are 'pure' java.
> 
> --
> Trygve Laugstøl
> 
> On Wed, 17 Dec 2003, Sonnek, Ryan wrote:
> 
> > Great idea Jason, and thanks for the advise.  I would MUCH rather be 
coding
> > java than writing xml.  The lure of Unit testing is also a huge bonus.
> >
> > Ummm....now, how do I go about it?  =)  I'm assuming that I must 
create
> > an Ant Task (don't know how to do this yet), then taskdef it inside my
> > plugin.jelly.  is there a developer's HOWTO available (on wiki?).
> >
> > Ryan
> >
> > -----Original Message-----
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, December 17, 2003 2:12 PM
> > To: Maven Developers List
> > Subject: Re: jelly intro
> >
> > On Wed, 2003-12-17 at 12:02, Sonnek, Ryan wrote:
> > > I'm a new plugin developer looking for resources on jelly scripting.
> > > To be exact, I'm looking for how to iterate through a list of 
folders
> > > and modify files that match a certain pattern.  any tutorials or
> > > examples you could point me to?  I've searched through the plugins I
> > > have installed, but haven't found anything yet that matches this.
> >
> > I would highly recommend you encapsulate your little tool in a POJO 
and
> > use the POJO from Jelly. So in Jelly you would end up with something
> > like:
> >
> > <toolbox:fileChanger
> >   directory="/my/dir"
> >   filepattern="**/*.txt"
> >   find="^monkey"
> >   replace="donkey"/>
> >
> > Then you can easily unit test it. Leverage your knowledge of Java, you
> > don't have to program in Jelly and I highly recommend you don't. Jelly
> > is an awesome integrator though and that's how you should use it. It's
> > dead simple to use a POJO from Jelly.
> >
> > > Thanks.
> > > Ryan
> 
> ---------------------------------------------------------------------
> 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