On 04/24/2009 09:09 AM, Jon Hardcastle wrote: > I like the idea of 2 installs - 1 database. I guess though that any > configuration stored in the DB would be common to both installs?
Correct. > The customisation are basically differing workflows and changes to severities > and things like that.. surface stuff but we have alot of projects and 2 > camps.. without inheritance that is hard to maintain. The biggest problem with inheritence is that the subproject model for MantisBT is far too flexible and complex. eg, you could have three projects A, B and C in a hierarchy like: A - C B - C where C is a subproject of both A and B. In this sort of case, how do you handle inheriting configurations that are present in both A and B? And this isn't even the most complex subproject hierarchy that MantisBT supports... -- John Reese LeetCode.net ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ mantisbt-help mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mantisbt-help
