> -----Original Message----- > From: Konstantin Priblouda [mailto:[EMAIL PROTECTED] > --- karthik Guru <[EMAIL PROTECTED]> wrote: > > > I needed access only to the metadata ( from Qdox) > > for the fileset that i selected. I wonder if there > > s'd be a default plugin that provides access to the > > metadata of all the files selected by fileset and > > accepts a template?. Basically it s'd take the > > location of the template from the build file instead > > of the usual expected location. > > Most plugins derive from base classes contained in > xdoclet / generama. That's place where this > functionality resides > > > > Does it make sense to have something like that? > > Ofcourse writing one is pretty trivial and that is > > what i did. Do you think it makes sense to ship a > > plugin like that? Also does it make sense to allow > > for overriding of the template file / location from > > outside (ie from build file)? > > You mean like template module from XD1 ? Maybe it > makes sense. > > Say there is some problem with ejb-jar.xml > > generation template, I can copy the existing one > > into my folder, modify it and run the EbJarXML > > plugin against the modified one instead of the one > > it shipped with? > > I think this discussion sall be taken to > xdoclet-plugins-interest list. There are more people.
I agree with Konstantin here - it would be better to use xdoclet-plugins-interest list. Regarding the overriding of EjbJarPlugin.jelly, it's a valid option - don't forget to include that in the classpath (in same package) before the plugin itself - I've made this a while ago - it's supposed to work. Btw, 1.0.3 that should be released soon has lots more improvements there - beware overriding EjbJarPlugin.jelly with the upgrade. I've been actively developing that plugin (and related) since a couple months ago - there was (is) lot of work to be done there. If you fell you can help improve it, fell free to contribute (through jira and mailing list). Regards Diogo
