[ http://jira.codehaus.org/browse/MNG-2719?page=comments#action_84968 ] Ole Ersoy commented on MNG-2719: --------------------------------
I prefer to keep this issue and any RPMMojo changes completely separate. I already have summary element on the mojo configuration of the model that is used to create the Spec file, but that summary element should map to a summary element on the pom so that collaboration between packagers and developers is simplified and streamlined, with maximum clearity with respect to what maps to what. Also I have already proposed one solution as to how new elements can be added quickly to the pom, without breaking backward compatibility. http://jira.codehaus.org/browse/MNG-1437 I think Jason is concerned that this could require rework on other Maven components that reference the Modello generated model directly, instead of the using the Plexus container, so I'll probably have to create a new Maven concept to examine whether this is true or not, and showing how to close the gap. Allthough breaking those components should be done anyways, so that they become inspired to use the Plexus container. If we wanna make an omellete we gotta break a few eggs. I'm already in the process of merging some of the elements of the existing RPM mojo into the new mojo. Thus this mojo eclipse's the features of the old one. Some of things in the mojo I created are there for the purpose of working with other mojo's in a model driven development context. Plus they are needed for some other work I'm doing with respect to setting up RPM repositories that mirror the Maven repository, while ensuring that Maven best practices are met. So what this means is that in order for the two to be merged, some leg work is required on your part. I'm going to publish a developer use case, and user use case document for the plugin. You will have to review this and understand the design changed, to see whether you are comfortable with the changes targeted at the developer use cases. Assuming you are fine with these, then I'll make sure the elements from the RPM mojo you created are merged into this mojo. The changes to the end user are fairly transparent. Instead of the Mapping elements being contained in the POM, they are moved to a different document that also targets a specific POM. Cheers, - Ole > Request for Summary element in POM > ---------------------------------- > > Key: MNG-2719 > URL: http://jira.codehaus.org/browse/MNG-2719 > Project: Maven 2 > Issue Type: New Feature > Reporter: Ole Ersoy > Priority: Minor > > If a summary element were added it would make RPM > Spec file generation more efficient, since spec files > "require" both a description and a summary. > A summary element can also be handy for > for other tools that want to generate reports > giving a summary, as well as a longer description > of the project. > If this sounds reasonable I will update the XML Schema for maven with the > summary > element and submit. > Cheers, > - Ole -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
