From bloodhound-dev-return-1575-apmail-incubator-bloodhound-dev-archive=incubator.apache.org@incubator.apache.org Mon Jan 14 18:09:31 2013 Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 48E43ECE0 for ; Mon, 14 Jan 2013 18:09:31 +0000 (UTC) Received: (qmail 84888 invoked by uid 500); 14 Jan 2013 18:09:31 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 84836 invoked by uid 500); 14 Jan 2013 18:09:30 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 84827 invoked by uid 99); 14 Jan 2013 18:09:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jan 2013 18:09:30 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of olemis@gmail.com designates 209.85.223.172 as permitted sender) Received: from [209.85.223.172] (HELO mail-ie0-f172.google.com) (209.85.223.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jan 2013 18:09:25 +0000 Received: by mail-ie0-f172.google.com with SMTP id c13so5381123ieb.17 for ; Mon, 14 Jan 2013 10:09:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=BPVaVBqZ9TxMcWrmtyPO3gj9MkuAzRkJijcGXQ4S2JM=; b=ULEVqH3cGwCh8KZ9b4uRk53NFQHeUcs90Ys0TOUEcZUPVECEKmpC/dYhR8RkEhi72h RcHnJmL76rQMcu/1kJvgfcbnNJGKlvlcZYZLHOzUYiKb9tccuPXUKYOoJEeCxUuCuI0L XlUHJ53rg9kfK9i4PP8Tp29iZUVNOcGV8HZzuq7dgYhJXoRWHk3wYvnoJ0CziUydhG18 IuvjurmJdAG4hYnHqekMjKh4F1LZSdLPqC+6wWrEJ+TMJnajIAsXHpkuXxjstzpCKp7V QJyLL+O2eCRCilw1/QwBsmeCXQBn2hinrEM6HMS6w7CkxTymgcs/h8/qi9ABBUhCbFZF Gcdw== MIME-Version: 1.0 X-Received: by 10.50.217.227 with SMTP id pb3mr2689574igc.0.1358186945542; Mon, 14 Jan 2013 10:09:05 -0800 (PST) Received: by 10.50.1.44 with HTTP; Mon, 14 Jan 2013 10:09:05 -0800 (PST) In-Reply-To: <50F4296B.9080209@digiverse.si> References: <053.0e57377525de9e84b59ecf4d36bdc79a@incubator.apache.org> <50F038FE.6000006@digiverse.si> <50F4296B.9080209@digiverse.si> Date: Mon, 14 Jan 2013 13:09:05 -0500 Message-ID: Subject: Re: [Apache Bloodhound] #323: Add support for custom hooks configurable through trac.ini From: Olemis Lang To: bloodhound-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On 1/14/13, Jure Zitnik wrote: > On 1/11/13 9:27 PM, Olemis Lang wrote: >> On 1/11/13, Jure Zitnik wrote: > [...] > > I'm aware of the configuration inheritance, the problem is that > inheritance by itself does not solve the issue. Let me try to elaborate > on the problem a bit more ;) > I kind of understand what you mean now . I'm of the idea that Trac's dispatch_request is not particularly useful for us . That's why I suggested in BEP 3 to get rid of it and override the dispatching system by generating our own deployment scripts , using our own entry points , etc ... ... about global.ini , well, I'm not sure right now what should I suggest about it . -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: