[
http://jira.codehaus.org/browse/MCHANGES-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=270213#comment-270213
]
Dennis Lundberg commented on MCHANGES-259:
------------------------------------------
2. That'd be great.
3. I prefer to have an interface, and an abstract class with common
implementation pieces. Also a JIRA subclass is better than a general purpose
Default implementation, since the implementation in there is specific to JIRA.
The patch for this issue doesn't contradict your original patch to make the
mappings configurable. IMO we should do both.
> Create modularity for supporting multiple issue management systems
> ------------------------------------------------------------------
>
> Key: MCHANGES-259
> URL: http://jira.codehaus.org/browse/MCHANGES-259
> Project: Maven 2.x Changes Plugin
> Issue Type: Improvement
> Components: other issue-trackers
> Affects Versions: 2.5
> Reporter: Benson Margulies
> Assignee: Benson Margulies
> Attachments: MCHANGES-259.patch
>
>
> In discussion of MCHANGES-245, Dennis notes the need for some global
> modularity for capturing the behavior of the different issue management
> systems. I'm creating this JIRA as a hat-rack to hang this work off of.
> My plan is to start by creating something very simple in the way of an
> abstract class, which can be elaborated as we go.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
