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: local policy includes SPF record at
 spf.trusted-forwarder.org)
Message-ID: <430A8246.1080403@gmail.com>
Date: Mon, 22 Aug 2005 21:56:22 -0400
From: Sachin Patel <sppatel2@gmail.com>
User-Agent: Mozilla Thunderbird 1.0+ (Windows/20050712)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: tooling patches
References: <430A6B4A.7050504@gmail.com>
 <5520FCCD-5378-4B7A-AAB3-547CB0BEA2D9@iq80.com> <430A7664.2070207@gmail.com>
 <09954976-1BD9-4A4D-8FF0-615202017B79@iq80.com>
In-Reply-To: <09954976-1BD9-4A4D-8FF0-615202017B79@iq80.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Oh really? I'm familiar with the project, but I wasn't aware that their 
building the plugins and features with Maven.  Let me pull down the 
source tommorow and see how and what their doing and then I'll respond. 

Sachin

Dain Sundstrom wrote:
> On Aug 22, 2005, at 6:05 PM, Sachin Patel wrote:
>
>> So I've held off on working on "how to build" after checking out  the 
>> source until all the project home related stuff gets worked  out.  
>> Building these plugins with maven will take some work.   As I  
>> mentioned before trying to build purely with maven isn't a good  
>> approach as there are alot of issues to do that.
>
> Can you explain why this isn't a good approach?
>
> There is a mavenide project that is building eclipse plugins for  
> using maven in eclipse, and these plugins themselves are built using  
> maven. http://mevenide.codehaus.org/mevenide-ui-eclipse/features.html
>
> Maybe we can just copy their build for this project.
>
> -dain
>