[ http://jira.codehaus.org/browse/MNG-2719?page=comments#action_84970 ] Ole Ersoy commented on MNG-2719: --------------------------------
Actually, There's an other alternative as well. I'm guessing your primary concern is that the introduction if the mojo I just created could fork developer attention, thus some ot the todo's on the current RPM mojo don't get done as quickly. I don't mind at all implementing those on my mojo, and then transferring them to yours as well. I'm already pretty familiar with the Codehaus RPM mojo. I think paralell mojo development might make sense in this case, since yours might satisfy the needs of developers that want to keep the mapping elements within the existing project, and mine Packagers who want a separate project. 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
