Seems like a hack because you don't want to have two descriptors to me. Personally, I'm ok with two descriptors - one for the 'project' part of a plugin and one for what the plugin adds to the build. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers
Jason van Zyl <[EMAIL PROTECTED]> wrote on 07/13/2002 11:54:32 PM: > On Fri, 2002-07-12 at 23:13, [EMAIL PROTECTED] wrote: > > Why the POM and not somewhere else ? Properties? > > Because the meta information can be attached to any object in the POM. > Get a little ugly with properties I think. > > > -- > > dIon Gillard, Multitask Consulting > > Work: http://www.multitask.com.au > > Developers: http://adslgateway.multitask.com.au/developers > > > > > > Jason van Zyl <[EMAIL PROTECTED]> wrote on 07/13/2002 01:01:18 AM: > > > > > Hi, > > > > > > I was just playing around with plugins and currently I'm using a normal > > > project.xml descriptor as a plugin is in essence a project. The only one > > > I've converted is the JXR plugin: it has sources, eventually some docs. > > > But other plugins like checkstyle have dependencies like the checkstyle > > > JAR, antlr and regex. > > > > > > I was thinking of making another plugin descriptor but I think I can get > > > away without doing it if we allow adding metainfo to the POM. So that > > > any element can have metainfo that can be utilized in any arbitrary > > > fashion. My example here is for the dependencies of a plugin: > > > > > > <dependencies> > > > <dependency> > > > <id>clover</id> > > > <version>1.0</version> > > > <metainfo> > > > <classloader>root</classloader> > > > </metainfo> > > > </dependency> > > > > > > <dependency> > > > <id>jdepend</id> > > > <version>1.0</id> > > > <metainfo> > > > <classloader>root.maven</classloader> > > > </metainfo> > > > </dependency> > > > </dependencies> > > > > > > So in the example the clover plugin needs pushed into the root > > > classloader while the jdepend jar is fine in the root.maven classloader. > > > > > > The metainfo could also be used to export reports the plugin provides or > > > whatever. I just want to try and reuse the project.xml and I think this > > > would be generally useful where projects might adding any sort of > > > information which they want to report on, or use for processing. Then if > > > particular items become widely used we can add them to the POM later on. > > > > > > -- > > > jvz. > > > > > > Jason van Zyl > > > [EMAIL PROTECTED] > > > http://tambora.zenplex.org > > > > > > In short, man creates for himself a new religion of a rational > > > and technical order to justify his work and to be justified in it. > > > > > > -- Jacques Ellul, The Technological Society > > > > > > > > > -- > > > To unsubscribe, e-mail: < > > > mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: < > > > mailto:[EMAIL PROTECTED]> > > > > -- > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > http://tambora.zenplex.org > > In short, man creates for himself a new religion of a rational > and technical order to justify his work and to be justified in it. > > -- Jacques Ellul, The Technological Society > > > -- > To unsubscribe, e-mail: < > mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: < > mailto:[EMAIL PROTECTED]> >
