On Fri, Jun 4, 2010 at 3:07 PM, Les Hazlewood <[email protected]> wrote: > It definitely doesn't have to sit in the POM file if that's considered > bad practice. The key is that the Plugin Portal would need to > download something lightweight to discover the metadata and not the > actual plugin. There is already a Grails plugin.xml file that they > use for this purpose, but it currently is bundled inside the plugin > .zip - not ideal. I'm sure that can be re-used. > The main goal though was to have that plugin.xml somewhere external to > the plugin .zip so the Plugin Portal can 'know' about the plugin and > not need to download it directly. I'll bring up your suggestions - I
Sounds like publishing the plugin.xml might be the right path since such a thing exists already. Jar plugin additionally packages the pom file by default into the jar, in this case you'd just need to do the opposite. You could very simply create a prototype configuration with the buildhelper plugin, see "Attach additional artifacts to your project" section at http://mojo.codehaus.org/build-helper-maven-plugin/usage.html. I'd designate a custom type, such as .gpm for that xml file though to make it easily identifiable. Kalle > On Fri, Jun 4, 2010 at 2:10 PM, Kalle Korhonen > <[email protected]> wrote: >> On Fri, Jun 4, 2010 at 1:28 PM, Les Hazlewood <[email protected]> wrote: >>> Is this possible? So, in addition to stuff like <developers>, is it >>> possible to add additional metadata? >>> plugins. >> >> Seems like a potential misuse of the pom.xml. The power of the project >> object model is that it's standardized and contains the metadata >> common to all projects (as much as possible). Even if you could do it, >> why would this custom metadata need to sit in the pom file if it's >> specific to a particular environment or technology only? Wouldn't be >> cleaner and simpler to to create a .gpm (Grails Plugin Metadata) with >> its own schema and whip up a plugin that reads it in from a >> pre-defined source location, possibly also adding it both to the zip >> and attaching it as a secondary artifact to the module? If you wanted >> to specify this metadata as part of the pom, you'd probably still want >> to create a custom plugin for it. The configuration section for a >> plugin can carry arbitrary xml data. For example, see jar plugin's >> manifest customization at >> http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html. >> You could follow the same approach for your custom plugin. >> >> Kalle >> >> --------------------------------------------------------------------- >> 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]
