« Return to Thread: Maven integration - feedback wanted

Re: Maven integration - feedback wanted

by mykol :: Rate this Message:

My 2cents..

I would really love to see Maven support be available in Grails eventually. Benefits that I see include:
- transitive dependency
- more transparent versioning for declared dependencies
- a better integrator between source code and IDEs via maven plugins such as maven eclipse plugin and maven idea plugin, or IDE plugin such as that of netbeans
- support for multi-module projects (imagine domains and services for example having a separate module with asynchronous versioning and producing separate jars)
- an open standard

That said, it won't be easy consolidating the different philosophies brought to the table.
- both have it's own standard directory layout
- both have it's own development lifecycle
- utilities of Grails are built-in via Groovy scripts. Maven via maven plugins

If Grails is to support Maven, I think there's gonna be a lot of compromise. So imho, it's either Grails fully adhere to the Maven philosophy, or pass up Maven support altogether and instead implement Maven's better features (like my previous suggestion).

On Thu, Jun 19, 2008 at 7:43 AM, Luke Daley <ld@...> wrote:

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

« Return to Thread: Maven integration - feedback wanted