Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=dk20050327; d=earthlink.net;
  b=Uqlb8OhQtvi2j8YaoZNZNW3e4gEUH33lvb90aEmyk8aIaIrC0vkhWHD1vHSMe6rf;
  h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Message-ID: <48615BF8.8090009@earthlink.net>
Date: Tue, 24 Jun 2008 16:41:28 -0400
From: Joe Bohn <joe.bohn@earthlink.net>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: [DISCUSS] Server Respository plugin for Geronimo 2.1+ - RC2
References: <484DFC93.6050001@earthlink.net>
 <48527A90.7060607@earthlink.net>	 <E40BFD4C-3A50-467A-85AE-7FD7EA55B4E2@gmail.com>
	 <4852B56E.7050406@earthlink.net>
 <add18bc80806241130k16aa542arc7f4f89a755bec45@mail.gmail.com>
 <48613F8C.5050506@earthlink.net> <486156CB.4070701@gmail.com>
In-Reply-To: <486156CB.4070701@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hernan Cunico wrote:
> Joe Bohn wrote:
>> Lin Sun wrote:
>>> Hi Joe, any plan to update the multi-repo documentation to instruct
>>> users to install the sample plugin instead of deploy the
>>> server-repo.xml file manually?
>>>
>>> Thanks, Lin
>>>
>>
>> Yes, I was planning to update the doc to include the installing the 
>> plugin once it was released.  However, I was thinking of keeping the 
>> manual process as well .... still hadn't decided on that yet.
>>
>> Joe
>>
> I would suggest we keep the manual process and then document the server 
> repo plugin as part of the sample apps (which are all plugins(*)). Then 
> we can reference to that section from the existing doc

No objection to keeping the manual process per say ... but this is not a 
sample.  Rather, it is a per server repository which can be used without 
any modification by the end user.  I think the description should remain 
independent of the samples.


> 
> (*) should we call the sample apps section sample plugins to give it a 
> more representative title?

I think it would be a mistake to change the title from apps to plugins. 
  They are still applications as well as plugins and a user looking for 
a sample will intuitively look for a sample application as the term 
plugin might not have any meaning to them.

> 
> Cheers!
> Hernan
>