Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 10303 invoked from network); 10 Feb 2006 13:31:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Feb 2006 13:31:25 -0000 Received: (qmail 89174 invoked by uid 500); 10 Feb 2006 13:31:24 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 89131 invoked by uid 500); 10 Feb 2006 13:31:24 -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 89120 invoked by uid 99); 10 Feb 2006 13:31:24 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Feb 2006 05:31:24 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of thorsten.scherler@wyona.com designates 195.226.6.68 as permitted sender) Received: from [195.226.6.68] (HELO mx1.wyona.com) (195.226.6.68) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Feb 2006 05:31:22 -0800 Received: from 242.red-213-97-135.staticip.rima-tde.net ([213.97.135.242] helo=[172.26.0.5]) by mx1.wyona.com with asmtp (Exim 3.35 #1 (Debian)) id 1F7YMW-00046G-00 for ; Fri, 10 Feb 2006 14:31:00 +0100 Subject: Re: [PROPOSAL] Plugin and themes naming convention From: Thorsten Scherler To: dev@forrest.apache.org In-Reply-To: <43EC8F4B.7040004@apache.org> References: <43EC8F4B.7040004@apache.org> Content-Type: text/plain; charset=utf-8 Date: Fri, 10 Feb 2006 14:30:53 +0100 Message-Id: <1139578254.7973.27.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N El vie, 10-02-2006 a las 13:04 +0000, Ross Gardler escribi=C3=B3: > Plugins are called something like: >=20 > org.foodomain.forrest.plugin.bar >=20 > i.e. "plugin" is singular >=20 > But we have two themes which: >=20 > org.apache.forrest.theme.Coat >=20 > and >=20 > org.apache.forrest.themes.core >=20 > i.e. "theme" and "themes" is used >=20 > I propose that we normalise on the existing naming convention used in=20 > plugins, i.e. we use "theme" (singular) >=20 -1 for theme. +1 for normalise. Since core is providing not only *one* theme (singular) but at least 3 (coat, pelt, common) it makes more sense to call theme packages "org.apache.forrest.themes.x". > ---- >=20 > On a related issue. We have no consistency in the naming of plugins. >=20 > I have tried to follow the Java convention of lower case for the=20 > "package" names and Camel case for the plugin name: >=20 > i.e. org.apache.forrest.plugin.input.FooBar >=20 > I propose that new releases of plugins should all conform to the camel=20 > case usage. We'll keep the current naming for already released plugins. hmm, I find it harder to use the Uppercase variant on linux and since java packages do not use uppercase in package names (e.g. package org.apache.lenya.transaction;). See above, I see plugins more as a packages and I am not very happy with naming them org.apache.forrest.plugin.input.FooBar because for me that is a package and not a Class. salu2 >=20 > Ross --=20 Thorsten Scherler COO Spain Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://lenya.apache.org thorsten.scherler@wyona.com thorsten@apache.org