Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=dk20050327; d=earthlink.net;
  b=iAR6ED4KG3jMztPCAqfOPaBrmAEs7tzSf2pNCCbA2ohj7aqrIdA/d/gAQzSU6iU/;
  h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Message-ID: <491EF83E.6030707@earthlink.net>
Date: Sat, 15 Nov 2008 11:26:38 -0500
From: Joe Bohn <joe.bohn@earthlink.net>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: grails plugin
References: <491DFF15.5030701@earthlink.net>
 <4F315024-9E6C-423C-B9F1-D5B408992E96@gmail.com>
In-Reply-To: <4F315024-9E6C-423C-B9F1-D5B408992E96@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jason Dillon wrote:
> Just curios why one would even bother with this?  Seems that this would 
> only be useful when someone deploys more than one grails-based app into 
> the sever... do folks even do that?  And what if the 2 apps evolve 
> differently and then need different versions of grails/groovy?

Yes, It's only useful if deploying more than one grails web app.  My 
thinking was that if a user has decided to work in a grails model the 
chances are probably good they'll be working multiple projects using the 
same model. My guess is that a user won't be maintaining multiple 
applications on multiple versions of grails (and deploying them to the 
same server) ... but I guess that is a possibility.  We would need to 
release a new version of the plugin for a new release of grails.


> 
> And then the need of tools to take a grails war and turn it into a 
> geronimo grails war... seems like too much work for little gain... and 
> in some respect some loss.

Yes, there is some work to generate the geronimo grails war.  I 
discovered an easy way to remove all of the external dependencies using 
a simple configuration change in the grails workspace.  However, the 
grails jars themselves are always included in the war.  So far the only 
way that I've been able to remove those too is by altering the 
war.groovy script.  So some more work is needed here.  Also, there is 
not yet a grails release that is distributing maven artifacts (but 
hopefully 1.1 will as they have snapshots deployed for this release).

> 
> How big are the dependencies anyways?

About 18MB.

> 
> --jason
> 
> 
> On Nov 15, 2008, at 5:43 AM, Joe Bohn wrote:
> 
>> I started some preliminary work on a grails plugin that could be used 
>> to collect all of the grails dependencies so that they can be shared. 
>> Along with this we would need to provide a mechanism to generate a war 
>> file in grails which does not contain any of the common elements.  I'd 
>> like to check in what I have thus far.  There is only one catch.  Some 
>> of the dependencies are Hibernate (LGPL).  I've updated my poms with a 
>> scope of provided for the hibernate dependencies.  Is that sufficient 
>> so that I can check the plugin into our SVN without any legal issues 
>> if somebody installs it?
>>
>> I'm also interested in additional thoughts on how to deal with the 
>> hibernate dependencies.  Should I consider using prerequisite instead 
>> of dependency so that they must be installed (I'm not yet sure if a 
>> grails application will work without hibernate but I suspect that it 
>> should)?
>>
>> Comments appreciated.  I'd really like to get this checked in under 
>> https://svn.apache.org/repos/asf/geronimo/plugins so it doesn't get 
>> lost even if it isn't quite ready for prime-time yet.
>>
>> Joe
> 
>