"Warner Onstine" <[EMAIL PROTECTED]> wrote on 30/09/2002 03:10:27 AM: > > ----- Original Message ----- > From: "Mr Dion Gillard" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Sunday, September 29, 2002 3:08 AM > Subject: Re: plug-ins and site documentation > > > > Most of the docs in the ref directory were very out of > > date, and since the source is long since gone and it's > > been confusing people, I removed it on last publish > > > > The docs need serious work. > > Yep, it has become very difficult to find information now. Someone might > want to look at redoing the whole directory setup or navigation setup.
What sort of information is hard to find? I'm open to suggestions on how we can make the docs and navigation better, but my opinion is only one. I'd prefer lots of people discuss this one. > > Can you tell me what you mean by seriously messed up? > > I thought the site was pretty much ok after the last > > publish. > > Sorry, mispoke. My sentence after that should've been the first. Now I > understand that the refs directory is gone completely. Will these be > updated? I'm in the process of updating the docs for the plugins, so that the goals and properties for each plugin are easy to find. What else needs to be back there? > I don't have time right now, but if I get a chance I will add some stuff to > the docs (like links to properties included in the plug-ins), or is this not > advised? Almost all plugins will have goals and properties, and hence should all have them documented along with the plugin. > > Re: Jalopy plugin - no idea, never used. Vincent has > > though. > > > > Installing plugins is just dropping the jar file in > > the maven.home/plugins directory. As far as the > > 'architecture' goes, it's pretty much there, though > > there are still some rough edges. > > This would be a great addition to the faq or users guide. Ok, I'll add it to my todo list. Anyone else feel free to submit a patch, or update the docs. > I saw: http://maven-plugins.sourceforge.net, will the plug-ins be moving > (and therefore not rely on the maven build process to wait for them)? Currently the plugins are not dependent on the main maven build. Each plugin is it's own subproject and can be built, versioned, documented and deployed separately. The plan is to keep the plugins as part of Maven, but for the sourceforge project to be a collection of plugins that may not be necessarily widely used (right Stephane?) > The biggest benefit I could see would be to add something like jEdit's > update feature, so that you could check for new plug-ins and download them. > jEdit also has a nice feature where the plug-in tells it what version of > jEdit requires in order to use them. This is in the works, but I don't think anyone's currently working on it. There's also a planned feature such that the project can define which version of a plugin it wants to use. > -warner -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
