[ http://jira.codehaus.org/browse/MNG-2719?page=comments#action_85063 ] Ole Ersoy commented on MNG-2719: --------------------------------
Oh OK - Great. It could be then that there are only architectural differences. I'm intending to use the one I built in the larger context of the RPM Creation and Quality Control Automation effort I have proposed on the mailing list, but I'm not saying that anyone else has to use it. It could be that both produce the same end result, and then everyone has a choice. One of the reasons I'm sticking with the EMF model generation is that it generates the baseline for the eclipse plugin that goes along with pom2spec mapping, so that we have a leg up on the corresponding eclipse work as well. Anyways, I'll publish all this soon, so that we have a clearer context for discussing various approaches and corresponding user and developer use case scenarios. 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
