« Return to Thread: Maven integration - feedback wanted
Re: Maven integration - feedback wanted
by tomas lin
::
Rate this Message:
Hi Peter,
Sounds amazing, the plugin management within a pom file is
definitively a great feature.
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.
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.
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?
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.
On Wed, Jun 11, 2008 at 8:57 AM, Peter Ledbrook <peter@...> wrote:
> Hi,
>
> 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:
>
> * all Grails JAR files are deployed to Maven with corresponding POMs
>
> * Maven/Gant integration so that Gant targets can be called from Maven
> and its plugins
>
> * package Grails' Gant scripts into a JAR file that can be declared as
> a project dependency
>
> * "grails create-app --maven" generates a pom.xml with the Grails
> dependencies included and the GMaven and Grails Maven plugins
> configured
>
> * "mvn compile" uses GMaven and the standard Java compiler instead of
> delegating to "grails compile"
>
> * Grails plugins declare their dependencies in Maven form (either as a
> pom.xml or in a Gant script)
>
> * Grails Maven plugin hooks into standard build cycle and copies files
> into the correct location for the War plugin
>
> I looked into a Grails archetype, but I can't really see a way of
> creating the Grails directory structure directly. So what I'm thinking
> of doing is having a simple archetype that installs a POM and then the
> user can run "mvn grails:initialize" or something like that to create
> the actual application files.
>
> What do people think? Some of the feedback will go into issue
> http://jira.codehaus.org/browse/GRAILS-38
>
> Cheers,
>
> Peter
>
> --
> Software Engineer
> G2One, Inc.
> http://www.g2one.com/
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Sounds amazing, the plugin management within a pom file is
definitively a great feature.
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.
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.
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?
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.
On Wed, Jun 11, 2008 at 8:57 AM, Peter Ledbrook <peter@...> wrote:
> Hi,
>
> 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:
>
> * all Grails JAR files are deployed to Maven with corresponding POMs
>
> * Maven/Gant integration so that Gant targets can be called from Maven
> and its plugins
>
> * package Grails' Gant scripts into a JAR file that can be declared as
> a project dependency
>
> * "grails create-app --maven" generates a pom.xml with the Grails
> dependencies included and the GMaven and Grails Maven plugins
> configured
>
> * "mvn compile" uses GMaven and the standard Java compiler instead of
> delegating to "grails compile"
>
> * Grails plugins declare their dependencies in Maven form (either as a
> pom.xml or in a Gant script)
>
> * Grails Maven plugin hooks into standard build cycle and copies files
> into the correct location for the War plugin
>
> I looked into a Grails archetype, but I can't really see a way of
> creating the Grails directory structure directly. So what I'm thinking
> of doing is having a simple archetype that installs a POM and then the
> user can run "mvn grails:initialize" or something like that to create
> the actual application files.
>
> What do people think? Some of the feedback will go into issue
> http://jira.codehaus.org/browse/GRAILS-38
>
> Cheers,
>
> Peter
>
> --
> Software Engineer
> G2One, Inc.
> http://www.g2one.com/
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
« Return to Thread: Maven integration - feedback wanted
| Free embeddable forum powered by Nabble | Forum Help |
