Return-Path: 
 <dev-return-46697-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 56116 invoked by uid 500); 22 Aug 2003 19:14:05 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 56050 invoked from network); 22 Aug 2003 19:14:04 -0000
Received: from unknown (HELO trinity.anyware-tech.com) (217.112.237.100)
  by daedalus.apache.org with SMTP; 22 Aug 2003 19:14:04 -0000
Received: (qmail 30397 invoked from network); 22 Aug 2003 16:27:19 -0000
Received: from unknown (HELO anyware-tech.com) (10.1.0.254)
  by trinity.anyware-tech.com with SMTP; 22 Aug 2003 16:27:19 -0000
Message-ID: <3F464466.7020506@anyware-tech.com>
Date: Fri, 22 Aug 2003 18:27:18 +0200
From: Sylvain Wallez <sylvain.wallez@anyware-tech.com>
Organization: Anyware Technologies
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4) Gecko/20030624
X-Accept-Language: fr, en, en-us
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: "Production" build for Cocoon?
References: <D0DB5D67DC3B1C4A92A3DB6849F3FEDD04573513@EXCHANGE.teranet.ca>
 <Pine.LNX.4.53.0308221630470.26783@lapgp.otego.com>
 <069c01c368c7$3d4812a0$1600a8c0@hypernexinc.local>
In-Reply-To: <069c01c368c7$3d4812a0$1600a8c0@hypernexinc.local>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Roger I Martin PhD wrote:

>standalone-demo build target is one of the worst ways to work with Cocoon; yet alone achieve what Chris is asking.  Cocoon is a super charged super powerful servlet that can be used to achieve some pretty amazing results.
>
>I've read the INSTALL.txt and it is a excellent example of unprofessional writing.  In fact it is simply obnoxious.
>  
>

Please don't forget that all Cocoon developers started as Cocoon users. 
So why don't you jump in and write some better install docs ? The 
community would be very thankful for this.

If sending patches is too complex, you can contribute to the Cocoon 
wiki, as many users do.

<snip/>

>For Cocoon developers: you need to start thinking of Cocoon as a servlet intended to be used "inside" of your customer's webapp.  If I opened an M$ product out of the box and the way to "INSTALL" it was described as in INSTALL.txt with the results far from "That's it!" I would not hesitate to return it.
>

Yeah, but with M$ you pay for that shiny box, have no way to make your 
feedback heard nor to contribute back.

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Orixo, the opensource XML business alliance  -  http://www.orixo.com