Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of jason.dillon@gmail.com
 designates 64.233.162.198 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:subject:date:to:x-mailer:from:sender;
        b=J79UMd0mF1xuut/kDD7s92SL4MfpRGB5uz/MZZ0snq7DzsdcFRHmAE3uaG9lZ+9iPnXtkWM4Vs0ZdsOPJZmA1H3kT8WRY2L+xKkOAFwPa63SOdJaRN6reSyrXXXj366DqRdCt3X2uRrT+bQSSiN4kh1OLoVDb8u68Xk9WmRnoJU=
Mime-Version: 1.0 (Apple Message framework v750)
In-Reply-To: <18FED0FF-06B8-4ED2-AD94-14FD7A7184CE@yahoo.com>
References: <449F57AF.50005@toolazydogs.com>
 <c278ac970606261305h5e5dd9e9sd7a174a1b30122da@mail.gmail.com>
 <A7F31A3C-0A6A-4B83-AAC8-AC1221C7E2A8@planet57.com>
 <44A0B169.105@toolazydogs.com>
 <18FED0FF-06B8-4ED2-AD94-14FD7A7184CE@yahoo.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9D79026C-057E-46A3-8E54-028F4562B2BC@planet57.com>
Content-Transfer-Encoding: 7bit
Subject: Re: Unable to build using m2
Date: Tue, 27 Jun 2006 13:59:08 -0700
To: dev@geronimo.apache.org
From: Jason Dillon <jason@planet57.com>
Sender: Jason Dillon <jason.dillon@gmail.com>

>> It's clear to me that we need to break out our plugins build and  
>> get the plugins published ASAP.  I asked this in another thread,  
>> what will it take to get this published?  I don't think that it's  
>> too much trouble, just an RTC to break the plugin out and then we  
>> just start publishing the snapshots.  We can shoot for a plugin  
>> release around the time of G v1.2.0>
>
> This is totally not clear to me.  All our plugins are going to  
> depend heavily on geronimo code, why would we try to publish them  
> separately or before the artifacts they depend on are published?

This is classic chicken and egg... having G depend on G plugins that  
also depend on G for the plugin to be built.

This might have worked before in m1, but so far I have not been able  
to get a plugin built and then used in the same build cycle with m2.

What parts of the build need these plugins?  Is it just the config  
modules?  If so then we may need to split the build into two chunks,  
one that builds the modules and plugins, and then another than builds  
the configs and assemblies.

--jason