On Fri, 2005-10-21 at 14:51 -0700, Jason van Zyl wrote: > On Fri, 2005-10-21 at 15:14 -0500, Allison, Bob wrote: > > In starting to build the RPM plugin, I was going to build an RPMArchiver > > plexus component, assuming that it might be useful for other uses. > > We got an RPM plug-in so maybe let us try to get it out in the open. We > at Mergere worked on one for a client and it would be nice if you didn't > have to redo it because we couldn't free it in time. Let me look into > it.
Ok, I got the go ahead to put the RPM out in the open. Give me a couple hours and I'll put them in the Mojo project. > > 1) Is there a problem having mojos and components in the same plugin? I > > was assuming that plexus would ignore the plugin.xml and mojo classes > > and that maven would ignore component.xml and the component classes. > > > > 2) How do I configure the plugin so that the plexus components are > > available? When I was looking at a lifecycle for RPM (about 2.0-beta-1) > > you had to specify <extension> in the <plugin> definition. The last > > time I looked at the project descriptor (it seems to be a broken link at > > present) there was a new section under <build> (IIRC) called > > <extensions> but I don't think that had configuration information in it. > > > > 3) I was putting the mojo classes in org.apache.maven.plugin.rpm and > > putting the plexus classes in org.codehaus.plexus.archiver.rpm. Is this > > reasonable or should I be using a different package for these items? > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
