From dev-return-81361-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Thu Nov 03 17:16:41 2005 Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 27380 invoked from network); 3 Nov 2005 17:16:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Nov 2005 17:16:37 -0000 Received: (qmail 74091 invoked by uid 500); 3 Nov 2005 17:16:34 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 74026 invoked by uid 500); 3 Nov 2005 17:16:33 -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 List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 74012 invoked by uid 99); 3 Nov 2005 17:16:33 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Nov 2005 09:16:33 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [68.230.240.38] (HELO eastrmmtao01.cox.net) (68.230.240.38) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Nov 2005 09:16:28 -0800 Received: from [192.168.0.100] (really [70.179.64.83]) by eastrmmtao01.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051103171536.ORHM13165.eastrmmtao01.cox.net@[192.168.0.100]> for ; Thu, 3 Nov 2005 12:15:36 -0500 Message-ID: <436A45DB.1030600@reverycodes.com> Date: Thu, 03 Nov 2005 12:16:11 -0500 From: Vadim Gritsenko User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [M10N] new repo layout References: <436A2490.9090302@reverycodes.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Jorg Heymans wrote: > Vadim Gritsenko wrote: > >>IIRC, we already have separated out blocks out of the core, into >> >> svn:/cocoon/blocks/ > > separating meaning to move them to a separate directory ? The flat > layout doesn't mean they aren't separated. Separating meaning they are separate projects with independent release cycles, as in: >>Where each block is treated as independent project, and has own >>tags/branches. With Cocoon 2.1.8 out this friday, several blocks will >>start having own tags. > > this concept works well with standard maven release management. > > >>Why do you want to reverse this and combine blocks with cocoon core? > > you mean combine them into the same directory ? I'm not sure I'm > following you here - can you elaborate a bit ? Yes, I mean why do you want to combine multiple projects into single uber project, in your proposed directory structure: /trunk /block-a /block-b Instead of having them as independent projects, as of now: /trunk /core /blocks /a /trunk /b /trunk It seems like a step backward, towards 2.1 situation, where each block is part of single project, instead of moving forward and cutting blocks loose... Vadim