Comments on: What is Right with Grails and Wrong with Maven http://www.juliesoft.com/2009/10/what-is-right-with-grails-and-wrong-with-maven/ solve niche problems, make users happy Mon, 22 Feb 2010 21:25:49 -0500 hourly 1 By: REVISITED: What is Right with Grails and Wrong with Maven | Jon Chase's Blog http://www.juliesoft.com/2009/10/what-is-right-with-grails-and-wrong-with-maven/comment-page-1/#comment-286 REVISITED: What is Right with Grails and Wrong with Maven | Jon Chase's Blog Tue, 20 Oct 2009 06:43:53 +0000 http://www.juliesoft.com/2009/10/15/what-is-right-with-grails-and-wrong-with-maven/#comment-286 [...] regard to my previous post, it looks like I pulled the Maven command from an old set of documentation. I believe the preferred [...]

[...] regard to my previous post, it looks like I pulled the Maven command from an old set of documentation. I believe the preferred [...]

]]> By: graham http://www.juliesoft.com/2009/10/what-is-right-with-grails-and-wrong-with-maven/comment-page-1/#comment-283 graham Sun, 18 Oct 2009 13:31:23 +0000 http://www.juliesoft.com/2009/10/15/what-is-right-with-grails-and-wrong-with-maven/#comment-283 maven was never integrated very well with grails because the main grails dev hates it. in my experience, ppl that hate maven haven't used it. i've had loads more problems trying to work with distributed ant than i have *ever* had with maven and its not as tho ivy makes the dep prob any easier, in fact you'll quickly have exactly the same probs. any each to their own, i can still use m-ant-p when i need it :) maven was never integrated very well with grails because the main grails dev hates it. in my experience, ppl that hate maven haven’t used it. i’ve had loads more problems trying to work with distributed ant than i have *ever* had with maven and its not as tho ivy makes the dep prob any easier, in fact you’ll quickly have exactly the same probs.

any each to their own, i can still use m-ant-p when i need it :)

]]> By: jonchase http://www.juliesoft.com/2009/10/what-is-right-with-grails-and-wrong-with-maven/comment-page-1/#comment-282 jonchase Sat, 17 Oct 2009 05:37:50 +0000 http://www.juliesoft.com/2009/10/15/what-is-right-with-grails-and-wrong-with-maven/#comment-282 I'll be the first to admit that maybe I'm missing something here WRT Maven. I pulled the Maven "create app" command line off of <a href="http://grails.org/Maven+Integration" rel="nofollow">this page from the Grails.org site</a>. Apparently that page points to <a href="http://forge.octo.com/maven/sites/mtg/grails-maven-plugin/" rel="nofollow">this page on an external site</a>, where "grails:create-app" is used to create a Maven based Grails project. I stand corrected! For the record, I still can't stand Maven. :) Give me Ant any day! I’ll be the first to admit that maybe I’m missing something here WRT Maven. I pulled the Maven “create app” command line off of this page from the Grails.org site. Apparently that page points to this page on an external site, where “grails:create-app” is used to create a Maven based Grails project.

I stand corrected!

For the record, I still can’t stand Maven. :) Give me Ant any day!

]]> By: Brian http://www.juliesoft.com/2009/10/what-is-right-with-grails-and-wrong-with-maven/comment-page-1/#comment-281 Brian Sat, 17 Oct 2009 03:24:36 +0000 http://www.juliesoft.com/2009/10/15/what-is-right-with-grails-and-wrong-with-maven/#comment-281 How about mvn archetype:generate ? You seem to have instructions from 2 years ago. How about mvn archetype:generate ? You seem to have instructions from 2 years ago.

]]> By: JS http://www.juliesoft.com/2009/10/what-is-right-with-grails-and-wrong-with-maven/comment-page-1/#comment-280 JS Fri, 16 Oct 2009 23:20:59 +0000 http://www.juliesoft.com/2009/10/15/what-is-right-with-grails-and-wrong-with-maven/#comment-280 I'm a big fan of both technologies, but this is not a good comparison, and I mean it. I’m a big fan of both technologies, but this is not a good comparison, and I mean it.

]]> By: Nils Breunese http://www.juliesoft.com/2009/10/what-is-right-with-grails-and-wrong-with-maven/comment-page-1/#comment-279 Nils Breunese Fri, 16 Oct 2009 12:29:36 +0000 http://www.juliesoft.com/2009/10/15/what-is-right-with-grails-and-wrong-with-maven/#comment-279 This is really comparing apples to eh... space ships. Or something. This is really comparing apples to eh… space ships. Or something.

]]> By: jens http://www.juliesoft.com/2009/10/what-is-right-with-grails-and-wrong-with-maven/comment-page-1/#comment-278 jens Fri, 16 Oct 2009 08:45:35 +0000 http://www.juliesoft.com/2009/10/15/what-is-right-with-grails-and-wrong-with-maven/#comment-278 It is unclear to me how you would create a 'JBoss Service Archive' with grails. (Sorry for the sarcasm) Typically, you would type 'mvn archetype:generate' and choose a project type, then answert the questions about group and artifact ids. Read more at http://maven.apache.org/plugins/maven-archetype-plugin/usage.html IMHO, it's not always a benefit for a tool like grails to run its own dependency reslution and build tool, because it does not integrate with a larger build, where the grails war is just a component. I have run in to that problem a couple of times and it's a pain to have the grails project to deviate from all other project policies and procedures. Source project layout, for example; where 3rd party libs are stored within the project. Then you have to create exclude rules for the version control system to prevent the libs to checkin. Another problem is temp files and some status info, that are stored outside the project directory, which means you cannot simple delete a ./target dir (or similar) to start out fresh. The grails clean command do not always clean up everything and sometimes one has to manually clean up the grails cache. Well, ... even the sun have spots. It is unclear to me how you would create a ‘JBoss Service Archive’ with grails. (Sorry for the sarcasm)

Typically, you would type ‘mvn archetype:generate’ and choose a project type, then answert the questions about group and artifact ids.
Read more at http://maven.apache.org/plugins/maven-archetype-plugin/usage.html

IMHO, it’s not always a benefit for a tool like grails to run its own dependency reslution and build tool, because it does not integrate with a larger build, where the grails war is just a component. I have run in to that problem a couple of times and it’s a pain to have the grails project to deviate from all other project policies and procedures.

Source project layout, for example; where 3rd party libs are stored within the project. Then you have to create exclude rules for the version control system to prevent the libs to checkin.

Another problem is temp files and some status info, that are stored outside the project directory, which means you cannot simple delete a ./target dir (or similar) to start out fresh. The grails clean command do not always clean up everything and sometimes one has to manually clean up the grails cache.

Well, … even the sun have spots.

]]>