Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 51886 invoked from network); 16 Oct 2006 09:04:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Oct 2006 09:04:16 -0000 Received: (qmail 88516 invoked by uid 500); 16 Oct 2006 09:04:15 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 88479 invoked by uid 500); 16 Oct 2006 09:04:15 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 88468 invoked by uid 99); 16 Oct 2006 09:04:15 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Oct 2006 02:04:15 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [203.121.192.7] (HELO mail.e-wire.net.au) (203.121.192.7) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Oct 2006 02:04:14 -0700 Received: from developer (mail.e-wire.net.au [127.0.0.1]) by mail.e-wire.net.au (8.13.1/8.13.1) with ESMTP id k9G93hlF021689 for ; Mon, 16 Oct 2006 17:03:48 +0800 Received: from 203-121-204-130.e-wire.net.au [203.121.204.130] for mail.e-wire.net.au (EHLO developer) via SMTP; Mon, 16 Oct 2006 17:03:48 +0800 From: "Gav...." To: Subject: Plugin Specific Stylsheets Date: Mon, 16 Oct 2006 17:03:31 +0800 Message-ID: <005701c6f101$f7894e70$650fa8c0@developer> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: AcbxAfNWU5csbkAhRtqYQ3jAoXyoGA== X-Antivirus: avast! (VPS 0641-4, 13/10/2006), Outbound message X-Antivirus-Status: Clean X-BitDefender-SpamStamp: 1.1.4 049000040111 X-BitDefender-Spam: No (0) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I think we touched on this before, at least I remember lots of Questions on how can it be done. As an example FOR-412 has a stylesheet in Jira ready to be applied But we don't know where to apply it (at least I don't). We don't want plugin specific stylesheets to be mixed up with Skin or theme stylesheets because they will be redundant to Those that don't use the plugin. Also things like images that Are for the projectinfo plugin reside in core when they should Also be in the plugin as they are plugin specific. So I had a thought. I wonder if we can create a /resources/css In the plugin, put any stylesheets in there, enable it with A 'plugin.stylesheet="yes"' in the plugins forrest.properties.xml And then get forrest to check for this when the 'forrest' gets built And adds it to the projects /resources/css and adds it to the rendered Output. Does that make sense. If so or not any ideas on how to get started? Once this plugin stylesheet problem is sorted then a few issues I think Can be closed, including FOR-412 to start with to test if the solution Works. Gav...