Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-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 0E039105FD for ; Tue, 21 Jan 2014 15:48:53 +0000 (UTC) Received: (qmail 79310 invoked by uid 500); 21 Jan 2014 15:48:52 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 79289 invoked by uid 500); 21 Jan 2014 15:48:52 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 79281 invoked by uid 99); 21 Jan 2014 15:48:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Jan 2014 15:48:52 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Jan 2014 15:48:47 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:References:In-Reply-To:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=6yF/OkUybQAkJfWO6UwDBj1bxz8zD2mH7GtWpChixJ4=; b=TcvisYIwTzWkYV23pOaanHFrZaUyyuWZ0mFCLKt8sDdjcU7wUDtJdbwF2IVHyC3l8cTIaWmyfMvCDxyfquTJ937s11Y1AcC2LNa9gbWShtb5BDrPcj5J1sRwaOKChXpDMw/rvCqIr4UlVewLohKseiww/DWnOu74Rf66Q9x+O8A=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-2.v29.ch3.sourceforge.com) by sfs-alluradaemon-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1W5dYw-0008QZ-KH for allura-dev@incubator.apache.org; Tue, 21 Jan 2014 15:48:26 +0000 Content-Type: multipart/related; boundary="===============6088857500691928794==" MIME-Version: 1.0 To: allura-dev@incubator.apache.org From: "Dave Brondsema" Reply-To: "[allura:tickets] " <6393@tickets.allura.p.re.sf.net> Subject: [allura:tickets] Re: #6393 Allow plugins to register new markdown macros Message-ID:

In-Reply-To:

References: <51c9c7a90594ca4a0571514e.tickets@allura.p.sourceforge.net>

Date: Tue, 21 Jan 2014 15:48:26 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============6088857500691928794== Content-Type: multipart/alternative; boundary="===============3176174545422893891==" MIME-Version: 1.0 --===============3176174545422893891== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Seems ok to me, as long as there won't be problems with 2 tools with the same name. I think you figured out some of that before.. disabling the original entry point perhaps? Will the tool name be the same so existing app configs from mongo load the overrided app? --- ** [tickets:#6393] Allow plugins to register new markdown macros** **Status:** in-progress **Created:** Tue Jun 25, 2013 04:39 PM UTC by Tim Van Steenburgh **Last Updated:** Thu Jan 16, 2014 08:20 PM UTC **Owner:** Tim Van Steenburgh Right now all of our markdown macros are defined in Allura core, even those that are tool-specific. We should provide a way for plugins to register their own macros with the platform. --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============3176174545422893891== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

Seems ok to me, as long as there won't be problems with 2 tools with the same name. I think you figured out some of that before.. disabling the original entry point perhaps? Will the tool name be the same so existing app configs from mongo load the overrided app?

[tickets:#6393] Allow plugins to register new markdown macros

Status: in-progress
Created: Tue Jun 25, 2013 04:39 PM UTC by Tim Van Steenburgh
Last Updated: Thu Jan 16, 2014 08:20 PM UTC
Owner: Tim Van Steenburgh

Right now all of our markdown macros are defined in Allura core, even those that are tool-specific. We should provide a way for plugins to register their own macros with the platform.

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============3176174545422893891==-- --===============6088857500691928794==--