On 11/06/2008, at 10:57 PM, Peter Ledbrook wrote:
> I have been looking into Grails/Maven integration in the last couple
> of days, and I would like some feedback from real Maven users on a
> proposal:
Sorry for the late reply.
> * all Grails JAR files are deployed to Maven with corresponding POMs
I am not entirely sure the jars need to be deployed to a repo. You
aren't going to eliminate the need to actually install grails on disk.
> * Maven/Gant integration so that Gant targets can be called from Maven
> and its plugins
Absolutely.
> * package Grails' Gant scripts into a JAR file that can be declared as
> a project dependency
Do you have a use case for this?
> * "grails create-app --maven" generates a pom.xml with the Grails
> dependencies included and the GMaven and Grails Maven plugins
> configured
Would be nice, but I think it's around the wrong way. I don't think
Grails should have to know about Maven: Maven should know about Grails.
> * "mvn compile" uses GMaven and the standard Java compiler instead of
> delegating to "grails compile"
What's the benefit here?
‘grails compile’ may introduce new magic in the future which we would
potentially miss out on. I don't see any benefit of not using grails'
own compile mechanism.
> * Grails plugins declare their dependencies in Maven form (either as a
> pom.xml or in a Gant script)
You can do this now in a roundabout way, have a look at the ldap plugin.
> * Grails Maven plugin hooks into standard build cycle and copies files
> into the correct location for the War plugin
Again, why? I would rather be 100% sure that when I build the WAR
with Maven I get the exact same war I would have got with ‘grails war’
p.s. I am not trying to be negative here, I desperately want this
functionality. I just want to make sure the right problems are being
solved.
LD.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email