Return-Path: Delivered-To: apmail-incubator-jackrabbit-dev-archive@www.apache.org Received: (qmail 76365 invoked from network); 7 Dec 2005 18:05:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Dec 2005 18:05:21 -0000 Received: (qmail 59427 invoked by uid 500); 7 Dec 2005 18:05:12 -0000 Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jackrabbit-dev@incubator.apache.org Delivered-To: mailing list jackrabbit-dev@incubator.apache.org Received: (qmail 59402 invoked by uid 99); 7 Dec 2005 18:05:12 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Dec 2005 10:05:12 -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 bcm@osafoundation.org designates 204.152.186.98 as permitted sender) Received: from [204.152.186.98] (HELO laweleka.osafoundation.org) (204.152.186.98) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Dec 2005 10:05:11 -0800 Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 67D101422DF for ; Wed, 7 Dec 2005 10:04:51 -0800 (PST) Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22239-06 for ; Wed, 7 Dec 2005 10:04:51 -0800 (PST) Received: from [10.0.1.4] (c-67-188-209-63.hsd1.ca.comcast.net [67.188.209.63]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 2BCD91422D7 for ; Wed, 7 Dec 2005 10:04:51 -0800 (PST) Message-ID: <43972442.20904@osafoundation.org> Date: Wed, 07 Dec 2005 10:04:50 -0800 From: Brian Moseley User-Agent: Thunderbird 1.5 (Macintosh/20051025) MIME-Version: 1.0 To: jackrabbit-dev@incubator.apache.org Subject: Re: FW: JCR, RMI & WebDAV - draft HOWTO *Correction* References: <7A47B13CD6A65B4E9722E401EEEBB34A2BF1B5@galadriel.intrinsica.co.uk> <4396F818.3060603@day.com> <439703F0.5000508@osafoundation.org> <43970747.2010608@zitting.name> <439708EC.2050800@osafoundation.org> <439721F2.4050401@zitting.name> In-Reply-To: <439721F2.4050401@zitting.name> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Jukka Zitting wrote: > Of course not, the issue I was trying to raise is where the > documentation should be located. i know, i was just being a smartass ;) > The current JCR-RMI documentation is embedded in the javadocs (the > package javadocs contain the end user instructions) and I kind of like > it that way, but at the moment the easiest way to access the docs is to > open and read the source files. :-( > > Perhaps I should just extract the user instructions from the javadocs > and set them up as a page on the main Jackrabbit web site. sounds like a good idea. i wish i'd had something like that for bdb as well. like probably most others, i'm impatient and just want to drop things into my app, twiddle a config file and be off and running. i don't want to have to read source code or javadocs, but i'm happy to refer to a one-page checklist/HOWTO. imo the holy grail is a series of these, one for each major contrib project/promoted subproject, in an obvious place on the web site. or maybe the wiki, so that users can help maintain them.