Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 83028 invoked from network); 17 Jan 2005 14:33:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 17 Jan 2005 14:33:33 -0000 Received: (qmail 44556 invoked by uid 500); 17 Jan 2005 14:33:04 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 44481 invoked by uid 500); 17 Jan 2005 14:33:04 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 44444 invoked by uid 99); 17 Jan 2005 14:33:03 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from wrinkledog.com (HELO wrinkledog.com) (207.162.210.50) by apache.org (qpsmtpd/0.28) with SMTP; Mon, 17 Jan 2005 06:33:01 -0800 Received: (qmail 17912 invoked by uid 0); 17 Jan 2005 14:33:17 -0000 Received: from unknown (HELO ?192.168.0.6?) (ml@67.171.172.83) by wrinkledog.com with SMTP; 17 Jan 2005 14:33:17 -0000 In-Reply-To: <5E091A68F794974CAF431CA31F5AF2CC11E9C7@server.bizzdesign.nl> References: <5E091A68F794974CAF431CA31F5AF2CC11E9C7@server.bizzdesign.nl> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: Bart Molenkamp From: Mark Lundquist Subject: Re: "Stripping" the Cocoon source tree Date: Mon, 17 Jan 2005 06:32:52 -0800 To: dev@cocoon.apache.org X-Mailer: Apple Mail (2.618) X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Dec 1, 2004, at 1:34 AM, Bart Molenkamp wrote: > Hi all, > > Is there any automated way for stripping the Cocoon source tree? I only > need the core code and some blocks. I want to remove unused blocks, > remove all samples, remove all documentation, remove as much tools as > possible, removing unused jars from lib/optional, etc. > > I want this, because I want to include the Cocoon source in my local > Subversion repository as a "vendor branch" (see the SVN book, > http://svnbook.red-bean.com/en/1.0/ch07s04.html) but I think that if I > add the entire Cocoon source tree to it, it might give performance > problems. See http://wiki.apache.org/cocoon/CocoonVendorBranch (just added! :-) > I'm also very curious how other people include Cocoon in their > repositories for their Cocoon-based applications (just a guess that > many > of you guys use Cocoon for other projects). The entire source tree, or > just the build (binary), or not at all? For me, it's not at all. I don't to a local Cocoon build within each project; I maintain builds of the Cocoon distro that I can share among many projects (although I can use a local Cocoon build for a project if need be). But until we get our real shared repository support into the Cocoon build system, I'm using a "Cocoon-centric" repository scheme, where the lib/ directory in the Cocoon build _is_ my repository. I have an ant task that copies WEB-INF from the 'coon build, then copies needed whatever additional jars it needs (e.g. Hibernate, Spring etc.) out of lib/optional. It's just easier that way. HTH, -ml-