Re: Maven integration - feedback wanted

> It seems counter-intuitive to have to use an archetype and then have
> to call another command to run a grails project. Maven already has a
> complicated and convoluted learning curve, and it seems like most
> maven users are very protective of this. I think that getting started
> with grails for maven users should be as plain vanilla maven as
> possible, otherwise you get into this weird "grailsfied maven" project
> that is unlike other maven projects.

OK, I'll look into this.

> Have you thought about putting the full grails stack under the
> <resources> tag of the archetype, this would mean the directory
> structure would be archetype/src/main/resources/grails-app and
> archetype/src/main/resources/web-app. This would allow me to run maven
> create without the extra structure problem.

I'm not sure whether "grails-app" should go under "src/main/resources"
since there are a lot of classes under "grails-app". I was thinking of
something like "src/main/grails".

> can we also have a grails update-pom or something like this that will
> generate a POM for existing projects that already have plugins defined
> rather than simply allowing pom creation at startup time?

Yes. I think that is a definite requirement.

> Will there be Gant scripts for each phase of the Maven lifecycle?  (
> http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Lifecycle_Reference
> ) . Right now, the Octo plugin has goals that are not visible to the
> user, it simply wraps gant calls for the proper places in the life
> cycle. But this makes extending the cycle much more difficult, it
> would be nice to have editable targets that wrap the existing grails
> targets, so for package, for example, we would have a grails War
> target, but also add our won custom targets.

I don't really understand this part. The existing Gant scripts will
pretty much stay as they are, I expect. For the package phase, I'm
planning on using the existing WAR plugin if possible.

One other thing to bear in mind is the plugins. I think to integrate
Grails nicely, Maven users we will have to sacrifice the Grails build
event mechanism, which may cause problems with some plugins. It
basically depends on how much use is made of the existing Gant scripts
from Maven builds. I haven't thought too hard about this because it's
painful :)

Cheers,

Peter

--
Software Engineer
G2One, Inc.
http://www.g2one.com/

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email