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. A Grails plugin is a .zip file, but the Grails environment > http://www.grails.org/plugin/home) need to read Grails-specific > metadata about that .zip without having to download the .zip first. > I'm proposing that the POM could serve that purpose *if* POMs can hold > additional metadata somehow.
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]
