From dev-return-7835-apmail-continuum-dev-archive=continuum.apache.org@continuum.apache.org Sun Feb 15 10:05:22 2009 Return-Path: Delivered-To: apmail-continuum-dev-archive@www.apache.org Received: (qmail 44680 invoked from network); 15 Feb 2009 10:05:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Feb 2009 10:05:22 -0000 Received: (qmail 71666 invoked by uid 500); 15 Feb 2009 10:05:22 -0000 Delivered-To: apmail-continuum-dev-archive@continuum.apache.org Received: (qmail 71623 invoked by uid 500); 15 Feb 2009 10:05:21 -0000 Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@continuum.apache.org Delivered-To: mailing list dev@continuum.apache.org Received: (qmail 71612 invoked by uid 99); 15 Feb 2009 10:05:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 Feb 2009 02:05:21 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of elpunzalan@gmail.com designates 209.85.221.20 as permitted sender) Received: from [209.85.221.20] (HELO mail-qy0-f20.google.com) (209.85.221.20) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 Feb 2009 10:05:14 +0000 Received: by qyk13 with SMTP id 13so2312213qyk.2 for ; Sun, 15 Feb 2009 02:04:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=4ULIrWn3TGWADAZkW28w89MBGGQiyQGhzHB6tsrxHww=; b=n4voz1upjODzBpyIn8xZQ0xDcL1ZKvW7MtnSMh7Ot/68GH/4J1ZAuFgRJCn7mxZ54m KM2vT9ulfecVSEffTmYV7k7SVFqGpOJzLQmcHYvryKjlsfFG2FuvyrtVbvwjfVYFec6U u47yo3H/bzdph537BttgjARkyZ28U+FisLVY0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=lVvTV6c58yALlZLCfUNMkIyN3FTXme3b0BdwzL7TRQaTliqJt4uz+DPnKsSZaesO/a 4zw66fhJU0lT+lFGB2kIgIBAZBINJ90vB/UeQxqywihrCJwuLT5u6L5zxd195ATlY+x2 bioZkRrl/XIrIHzUi/aw1kN0yolQAthDudZvE= MIME-Version: 1.0 Received: by 10.224.89.74 with SMTP id d10mr6123965qam.380.1234692293168; Sun, 15 Feb 2009 02:04:53 -0800 (PST) In-Reply-To: References: <958977410902120108g4c2f00d7n4f323b00ac23bb1a@mail.gmail.com> Date: Sun, 15 Feb 2009 02:04:53 -0800 Message-ID: <958977410902150204q1981335ejc61283c75eb0ff08@mail.gmail.com> Subject: Re: thoughts on CONTINUUM-745 From: Edwin Punzalan To: dev@continuum.apache.org Content-Type: multipart/alternative; boundary=0015175ccfb88a8f8f0462f233eb X-Virus-Checked: Checked by ClamAV on apache.org --0015175ccfb88a8f8f0462f233eb Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Thanks, Brett. Btw, I just realized that my proposal will affect (or will be affected by) the "non-recursive" option when adding a new maven project. I searched and found CONTINUUM-798 which is currently assigned to Jesse. Wendy did raise the problem about the non-recursive projects. I'm guessing my suggestion above will prevent it. Anyway, the issue is not In Progress but I'll wait and see what Jesse has to say with my comment in there. On Sat, Feb 14, 2009 at 6:53 AM, Brett Porter wrote: > > On 12/02/2009, at 5:08 PM, Edwin Punzalan wrote: > > Hi, guys. >> >> >> I've been out for quite some time and now that I have some spare time, I >> hope you don't mind me looking through jira again. ^_^ >> > > \o/ > Welcome back :) > > As suggested, I looked at a solution that involves a checkout of the poms >> from the SCM: >> > > What about checking out the entire first project (since that'll have to > happen anyway), then read the POMs from the filesystem? > > That's actually very close to (or a step towards), this: > > And then I thought of an alternative (ambitious?) way to accomplish this: >> >> Right now, when a parent pom is in a project group and a new module is >> added >> to it, continuum will not discover this and doesn't create a new project >> for >> that new module (right?). So what I have in mind is to add a new action >> (button?) that will look through all parent poms in the project group, >> determine if there are modules which do not have a corresponding continuum >> project and create them. We can even add this action to the standard >> build >> workflow of continuum for auto-discovery. >> > > That's a very highly desired feature, so if you're able to do so it would > be great to have :) > > >> >> Then we can reuse this same action for CONTINUUM-745... that is, add the >> multi-project pom into continuum (ignoring its modules during add) to >> create >> just one continuum project to the project group. And then the user can >> choose to execute this action (or maybe its automatic after checkout?) so >> that continuum projects will be created for its modules and added to the >> project group. >> > > Yes, this would certainly work! > > Cheers, > Brett > > -- > Brett Porter > brett@apache.org > http://blogs.exist.com/bporter/ > > --0015175ccfb88a8f8f0462f233eb--