The extensions element is mostly an optimisation - we'd have to initialise all plugins up front otherwise which is quite annoying (eg, when you run clean and have to download things).
In the future, dynamic maps in the plexus container will make the extensions element redundant. Thanks for volunteering to improve the documentation - the plugin guide sounds like the right place to put it. There is some similar docs in the lifecycle guide that perhaps should be put into the same section (plugins that provide extensions to maven). - Brett On 11/10/05, David Jackman <[EMAIL PROTECTED]> wrote: > Oh, my bad. I forgot the part about <extensions>true</extensions> when > using the plugin. It seems to work now. > That is unfortunate that I have to add that. Why isn't the default to > use any extensions provided by the plugin? Maybe I'm not clear on what > the extensions tag means (it's not documented at all). > > ..David.. > > -----Original Message----- > From: David Jackman [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 09, 2005 9:42 AM > To: Maven Users List > Subject: RE: [m2] Custom artifact types (and the handlers who love them) > > So, if I understand correctly, I want to put a components.xml file in my > plugin's src/main/resources/META-INF/plexus directory? And that should > look like the components.xml file in that place in the maven-artifact > project (except that it defines only the artifact handler for my new > artifact type)? That didn't seem to work. > > Where would the docs for this go? Into the Guide for Developing > Plugins? > When I get it all to work for me, I'll add my knowledge to the docs for > future generations. > > ..David.. > > > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 08, 2005 6:44 PM > To: Maven Users List > Subject: Re: [m2] Custom artifact types (and the handlers who love them) > > Yes, while the docs are lacking in this area it is very similar to the > build lifecycle which is documented. > > - add components.xml with handler reference (see maven-artifact for > examples) > - when using the plugin, set <extensions>true</extensions> to make the > type available. > > On 11/9/05, David Jackman <[EMAIL PROTECTED]> wrote: > > I've created a Mojo that generates a Javadoc-like documentation set, > > and my plugin does things similar to the javadoc plugin in that it > > archives all of the docs into a jar file and attaches the artifact to > the list. > > In looking at the artifact code, however, it looks like it's trying to > > > find an artifact handler for my custom artifact type so it knows how > > to work with it (specifically, I'm trying to dictate what the file > > extension should be). How do I create and register an artifact > > handler for my artifact type? I assuem that my plugin would take care > > > of this sort of thing? > > > > ..David.. > > > > > > > > --------------------------------------------------------------------- > 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]
