Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (athena.apache.org: domain of elpunzalan@gmail.com
 designates 209.85.221.20 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=leTW5ndAf2dOKFQsr+rkXtkrBJqrXA6L2kWC+jl/e0SKasMq0SS37Li+pH7JDPjXNB
         R3Q0QJeWLds5lRNUprilJp//Rz/JphIkstoIFFNheqA2QIsM1XtMUC0niUWbT+1DEcP6
         072PR3NJQlZCw1cHCP2e6X9RPYZnGRBrXmw7M=
MIME-Version: 1.0
Sender: elpunzalan@gmail.com
In-Reply-To: <DD8410A1-AEE3-4C66-AB02-1DFAF0769CB1@apache.org>
References: <958977410902120108g4c2f00d7n4f323b00ac23bb1a@mail.gmail.com>
	 <DD8410A1-AEE3-4C66-AB02-1DFAF0769CB1@apache.org>
Date: Sun, 15 Feb 2009 02:15:35 -0800
Message-ID: <958977410902150215n271a006ma53cada627091a0a@mail.gmail.com>
Subject: Re: thoughts on CONTINUUM-745
From: Edwin Punzalan <epunzalan@apache.org>
To: dev@continuum.apache.org
Content-Type: multipart/alternative; boundary=0015175743b6d3e2f50462f2594e

--0015175743b6d3e2f50462f2594e
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 <brett@apache.org> 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/
>
>

--0015175743b6d3e2f50462f2594e--