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: domain of jason.dillon@gmail.com
 designates 209.85.142.185 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:in-reply-to:content-type
         :content-transfer-encoding:mime-version:subject:date:references
         :x-mailer;
        b=mU5toG7fr0UAHIBmJwIOe4G9XYf0oCCgDO19xQqRuHyAoFMUEsH07dJGEYy9WwL8e9
         cDTOKeRUYAmOdJV26VxZLQzj0lsSW2XFEFhWmTg/4jyIgF2DNB0gxEDrIglV2d8yTfYH
         QrJ7Ts3tBz9GqyZm14eR2cCicrzGoZTEuvVxE=
Message-Id: <90042FF4-2D94-40D6-ADC2-FD6B01AF7FAC@gmail.com>
From: Jason Dillon <jason.dillon@gmail.com>
To: dev@geronimo.apache.org
In-Reply-To: <491EF83E.6030707@earthlink.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: grails plugin
Date: Mon, 17 Nov 2008 09:28:25 +0700
References: <491DFF15.5030701@earthlink.net>
 <4F315024-9E6C-423C-B9F1-D5B408992E96@gmail.com>
 <491EF83E.6030707@earthlink.net>

On Nov 15, 2008, at 11:26 PM, Joe Bohn wrote:
> 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.

Well, I guess it can't hurt to provide this for folks... just not sure  
the effort is worth it at the moment, but I could be wrong.


>> 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).

I suppose you could use TrueZIP to just delete them from the war, or  
with some Ant muck to unwar, delete, rewar.


>> How big are the dependencies anyways?
>
> About 18MB.

Yikes. :-\

--jason