You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <de...@bloodhound.apache.org> on 2013/04/18 16:26:09 UTC

[Apache Bloodhound] #504: Noting component incompatibility in admin panel

#504: Noting component incompatibility in admin panel
--------------------+---------------
  Reporter:  gjm    |    Owner:
      Type:  task   |   Status:  new
  Priority:  major  |  Version:
Resolution:         |
--------------------+---------------
 If we don't have the ability already we should be able to let components
 declare that they are incompatible with others being active.

 This might help with #373 for example.

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/504>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #504: Noting component incompatibility in admin panel

Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#504: Noting component incompatibility in admin panel
--------------------------+----------------------------------
  Reporter:  gjm          |      Owner:  olemis
      Type:  enhancement  |     Status:  accepted
  Priority:  major        |  Milestone:
 Component:  trac core    |    Version:
Resolution:               |   Keywords:  component dependency
--------------------------+----------------------------------
Changes (by olemis):

 * keywords:   => component dependency
 * status:  new => accepted
 * component:  plugins => trac core
 * owner:  nobody => olemis


Comment:

 I have a idea consisting in patching Trac core . I'll try to sketch it .

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/504#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #504: Noting component incompatibility in admin panel

Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#504: Noting component incompatibility in admin panel
--------------------------+----------------------------------
  Reporter:  gjm          |      Owner:  olemis
      Type:  enhancement  |     Status:  accepted
  Priority:  major        |  Milestone:  Unscheduled
 Component:  trac core    |    Version:
Resolution:               |   Keywords:  component dependency
--------------------------+----------------------------------
Changes (by rjollos):

 * milestone:   => Unscheduled


Comment:

 Another possibility would be to allow Components to disable other
 Components. Therefore if we require that `trac.ticket.web_ui:TicketModule`
 be disabled when `multiproduct.ticket.web_ui.ProductTicketModule` is
 enabled, we could provide functionality in the Trac core such that
 `ProductTicketModule` disables the `TicketModule`.

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/504#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #504: Noting component incompatibility in admin panel

Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#504: Noting component incompatibility in admin panel
--------------------------+--------------------
  Reporter:  gjm          |      Owner:  nobody
      Type:  enhancement  |     Status:  new
  Priority:  major        |  Milestone:
 Component:  plugins      |    Version:
Resolution:               |   Keywords:
--------------------------+--------------------
Changes (by gjm):

 * owner:   => nobody
 * type:  task => enhancement
 * component:   => plugins


-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/504#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker