incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <bloodhound-...@incubator.apache.org>
Subject Re: [Apache Bloodhound] #23: quick ticket should check for correct ticket module to use
Date Sun, 15 Apr 2012 19:09:38 GMT
#23: quick ticket should check for correct ticket module to use
------------------------+-------------------------------------
  Reporter:  gjm        |      Owner:  gjm
      Type:  defect     |     Status:  new
  Priority:  major      |  Milestone:  RC1 for initial release
 Component:  dashboard  |    Version:
Resolution:             |   Keywords:
------------------------+-------------------------------------

Comment (by gjm):

 I can't see any particular problem with subclassing a component,
 particularly in the case where the parent class is meant to be deactivated
 to when the subclass is active.

 Meanwhile, I don't want to be attempting to find out what component is
 associated with the /newticket path if we do not know that this is always
 the correct path. I may misunderstand what is possible here of course.

 A simple alternative to my suggestion in comment:2 would be to see if
 Bloodhound's replacement !TicketModule is installed and active before
 checking on the original !TicketModule.

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/23#comment:6>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker

Mime
View raw message