geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Dillon <>
Subject Re: grails plugin
Date Sat, 15 Nov 2008 04:46:57 GMT
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?

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.

How big are the dependencies anyways?


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

>  so it doesn't get lost even if it isn't quite ready for prime-time  
> yet.
> Joe

View raw message