#695: Add support for the CommitTicketUpdater component
--------------------------+-----------------------
Reporter: bsmithers | Owner: rjollos
Type: enhancement | Status: review
Priority: major | Milestone: Release 8
Component: trac core | Version: 0.7.0
Resolution: | Keywords: vcs hooks
--------------------------+-----------------------
Comment (by olemis):
Replying to [comment:18 rjollos]:
> * [attachment:t695_r1545950_twill_write_html.diff] will be included in
[trac:milestone:1.0.2 Trac 1.0.2] (trac:#11440, trac:#10018).
> * Part of
[attachment:t695_r1534486_commit_ticket_update.tests.func.diff] committed
to Trac in [trac 12434] for inclusion in Trac 1.0.2 (trac:#11440).
>
> I think we should see if it is possible to subclass
`CommitTicketUpdater` rather than modifying it
([attachment:t695_r1534486_commit_ticket_update_checklinks.diff]). At
least, this approach has worked well for other situations: trac:#11349,
trac:#10755.
Well , the fact is that the notion of multi-product has been there since
the beginning . I mean , all previous patches are built under the
assumption that the component is operating in a multi-product environment
. Subclassing may be an option , and I'm not against doing so , but ...
why bother if the component is already aware of multi-product architecture
?
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/695#comment:19>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
