[ http://jira.codehaus.org/browse/MNG-2719?page=comments#action_84391 ] Ole Ersoy commented on MNG-2719: --------------------------------
If there is a shortDescription element already,I think that would be the most ideal thing to map to...but I don't see one in the Schema? Name I think suggests something a lot different from than summary. I'm trying to make the process as clean and simple as possible. Right now I have a summary property on the EMF model that I'm mapping the Maven pom to, and if the Maven Schema / Model had a summary element then this would make the collaboration between RPM packagers and builds that use Maven more streamlined and clean. Here's what could happen if there is no summary or short description field in Maven. The RPM Packager wants to set the Spec Headings. She gets to the Summary heading of the Spec. What should it map to. The people that own the build did not really put a suitable value in the in the POM she feels, so she just enters a value in manually in the JPackage RPM generator project. This project is completely separate from the original build. It's artifact is an RPM and SRPM only. So in short: She has to do more work, because the POM does not have what she needs. Now if the POM had a summar element it could be that the owners of the POM filled it in and she could use it. But suppose they did not. If she fills it it, it's likely that she wants it maintained on the POM and that she'll contact the pom owners to have it added. This streamlines the work and captures it. That's the goal. It's a fairly minor thing, but when multiplied by all the Maven projects out there it could represent a substantial saving in effort. Then when you start to consider other capabilities that could benefit from the Summary element as well, like reporting, the benefits multiply. > 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
