Nexus can utilize anything contained in the repository. Whether a piece of metadata exists alongside the artifact or within it, a Nexus plugin could be created to process the information. So you don't need to change the way Grails plugins are packaged in order to extract the metadata and make it available. We know from experience that Nexus is perfect for plugin systems :-)
On Jun 4, 2010, at 4:28 PM, Les Hazlewood wrote: > Is this possible? So, in addition to stuff like <developers>, is it > possible to add additional metadata? > > I'm asking because the Grails development team is exploring the > possibility of using a Maven repository (e.g. Nexus) to host Grails > plugins. A Grails plugin is a .zip file, but the Grails environment > (and the global Grails Plugin Portal > 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. > > Any ideas? > > Thanks, > > Les > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl ---------------------------------------------------------
