You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2010/12/31 13:55:58 UTC

[jira] Updated: (MCHANGES-211) Restructure the announcement goal to make it easier to add other issue management systems

     [ http://jira.codehaus.org/browse/MCHANGES-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg updated MCHANGES-211:
-------------------------------------

      Description: 
The AnnouncementMojo is currently very hardwired to create announcements based on a changes.xml file. On top of that support was added to allow using JIRA instead. Later the option to merge release info from both changes.xml and JIRA was included.

The design of this isn't at all extendable. If you wanted to add another issue management system you would have to add several configuration options just to handle which issue management system(s) should be used. I plan to deprecate the parameters {{boolean generateJiraAnnouncement}} and {{boolean jiraMerge}} and to add a new parameter {{List issueManagementSystems}} to replace them.

  was:
The AnnouncementMojo is currently very hardwired to create announcements based on a changes.xml file. On top of that support was added to allow using JIRA instead. Later the option to merge release info from both changes.xml and JIRA was included.

The design of this isn't at all extendable. If you wanted to add another issue management system you would have to add several configuration options just to handle which issue management system(s) should be used. I plan to deprecate the parameters {{boolean generateJiraAnnouncement}} and {{boolean jiraMerge}} and a new parameter {{List issueManagementSystems}} to replace them.

    Fix Version/s: 2.4
         Assignee: Dennis Lundberg
          Summary: Restructure the announcement goal to make it easier to add other issue management systems  (was: Restructure the announcement goal to make it easier to add other issue managements systems)

> Restructure the announcement goal to make it easier to add other issue management systems
> -----------------------------------------------------------------------------------------
>
>                 Key: MCHANGES-211
>                 URL: http://jira.codehaus.org/browse/MCHANGES-211
>             Project: Maven 2.x Changes Plugin
>          Issue Type: Improvement
>          Components: announcement
>    Affects Versions: 2.3
>            Reporter: Dennis Lundberg
>            Assignee: Dennis Lundberg
>             Fix For: 2.4
>
>
> The AnnouncementMojo is currently very hardwired to create announcements based on a changes.xml file. On top of that support was added to allow using JIRA instead. Later the option to merge release info from both changes.xml and JIRA was included.
> The design of this isn't at all extendable. If you wanted to add another issue management system you would have to add several configuration options just to handle which issue management system(s) should be used. I plan to deprecate the parameters {{boolean generateJiraAnnouncement}} and {{boolean jiraMerge}} and to add a new parameter {{List issueManagementSystems}} to replace them.

-- 
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