Hi, Olemis Lang wrote: > > <[email protected]> wrote: > >> It would be quite a manageable job to integrate the approach of > >> having multiple projects in one Trac instance in a way like > >> SimpleMultiProjectPlugin or Bloodhound does. But as far as I > >> understood the situation, the difficulty, why nobody started to > >> implement it, is that such approach should be at the same time > >> generic enough that it is able to handle multiple projects spread around > multiple Trac instances. > > I'm not sure I get all the implications of the paragraph above
"Multiple Trac instances" (in the sense of http://trac.edgewall.org/wiki/TracDev/Proposals/MultipleProject) means to have several independent Trac installations, each one with its own trac.db and representing one project, and you also have a master frontend that handles them all in a multiple-project web-interface. This approach is harder to implement than to introduce a new "project" dimension in a single Trac instance, which is a system with only one trac.db file. , but jftr > Apache(tm) Bloodhound implements full support for multiple projects , in the > sense that new (product) environments are implemented inside the (now > global) environment , thus sharing a single DB . This is called SingleEnvironment (see http://trac.edgewall.org/wiki/TracMultipleProjects/SingleEnvironment). > > It would be better not to end up with 2 different implementations for > > this MultiProject feature. > > > > jftr Bloodhound is quite different to SimpleMultiprojectPlugin , just choose > the one that better fits your particular purpose . Maybe it's a good idea to create a wiki page on trac.edgewall.org that explains/lists the feature differences between all those multiple-project solutions in one table or survey, respectively. This is what the Trac user actually wants on his search for what to decide. From time to time I also read user postings where they even haven't understood the difference between Trac installations/instances, user projects and source repositories. That's why it makes it even harder to understand it for Trac newbies if there are several approaches or solution for how to deal with user projects. CU, F@lk ---- R&D Software Baumer Optronic GmbH www.baumer.com Gesch?ftsf?hrer: Dr. Albert Schmidt* Dr. Oliver Vietze Sitz der Gesellschaft: Radeberg Amtsgericht Dresden: HRB 15379 Ust. ID: DE 189714583 -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/groups/opt_out.
