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] #280: Move multiproduct.model.ModelBase to dashboard plugin
Date Fri, 07 Dec 2012 22:39:13 GMT
#280: Move multiproduct.model.ModelBase to dashboard plugin
---------------------------+------------------------------------
  Reporter:  olemis        |      Owner:  franco
      Type:  enhancement   |     Status:  review
  Priority:  trivial       |  Milestone:
 Component:  multiproduct  |    Version:
Resolution:                |   Keywords:  database model testing
---------------------------+------------------------------------

Comment (by rjollos):

 Replying to [comment:6 olemis]:
 > At the time there was no much time to create and manage a new
 bloohound_core directory that noone knew what'd happen with it in the
 future . After considering both options we decided that shared assets
 would be placed in dashboard because all other plugins already depended
 upon it (for widgets).

 Yeah, I understand. Been there ;)

 This ticket might not be the best place to tackle such a major
 reorganization. I'm also wondering if all of the `bloodhound_*` plugins
 should become a single plugin, so that we can have a single `setup.py` and
 a directory structure like:
 {{{
 bloodhound/model.py
 bloodhound/dashboard
 bloodhound/search
 }}}
 This would in some ways mirror the directory structure of Trac. Are there
 reasons we wouldn't want to do this?

 I"m inclined to commit Franco's latest patch and leave these
 reorganization issues for another ticket.

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

Mime
View raw message