<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Grails and Maven with no Maven</title>
	<atom:link href="http://www.mjwall.com/2009/01/grails-and-maven-with-no-maven/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mjwall.com/2009/01/grails-and-maven-with-no-maven/</link>
	<description>Just a guy and his computer</description>
	<pubDate>Fri, 24 May 2013 13:14:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: mjwall</title>
		<link>http://www.mjwall.com/2009/01/grails-and-maven-with-no-maven/#comment-172</link>
		<dc:creator>mjwall</dc:creator>
		<pubDate>Mon, 07 Dec 2009 13:31:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.mjwall.com/?p=89#comment-172</guid>
		<description>The pom that is generated in this example does not have a parent entry.  To overcome the settings.xml issue, notice the builder for the deploy task creates a distributionManagement tag.

I would not use for a multi-module project.  The grails and maven integration has come a long way since I wrote this post.  Try http://grails.org/Developer+-+Maven+Integration

I wrote an article in the Nov issue of groovymag, see http://www.groovymag.com/main.issues.description/id=15/.  The article is about mavenizing and existing grails project.

Good Luck.</description>
		<content:encoded><![CDATA[<p>The pom that is generated in this example does not have a parent entry.  To overcome the settings.xml issue, notice the builder for the deploy task creates a distributionManagement tag.</p>
<p>I would not use for a multi-module project.  The grails and maven integration has come a long way since I wrote this post.  Try <a href="http://grails.org/Developer+-+Maven+Integration" rel="nofollow">http://grails.org/Developer+-+Maven+Integration</a></p>
<p>I wrote an article in the Nov issue of groovymag, see <a href="http://www.groovymag.com/main.issues.description/id=15/" rel="nofollow">http://www.groovymag.com/main.issues.description/id=15/</a>.  The article is about mavenizing and existing grails project.</p>
<p>Good Luck.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://www.mjwall.com/2009/01/grails-and-maven-with-no-maven/#comment-171</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Mon, 07 Dec 2009 11:36:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.mjwall.com/?p=89#comment-171</guid>
		<description>Do you still think this is the best way to do this?  I am having trouble getting your script to use a parent POM.  I think this is due to it not reading the repository locations in my settings.xml, which is a problem you noted.  Could you expand on how you fixed that?

Thanks.</description>
		<content:encoded><![CDATA[<p>Do you still think this is the best way to do this?  I am having trouble getting your script to use a parent POM.  I think this is due to it not reading the repository locations in my settings.xml, which is a problem you noted.  Could you expand on how you fixed that?</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mjwall</title>
		<link>http://www.mjwall.com/2009/01/grails-and-maven-with-no-maven/#comment-142</link>
		<dc:creator>mjwall</dc:creator>
		<pubDate>Sun, 11 Jan 2009 03:52:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.mjwall.com/?p=89#comment-142</guid>
		<description>Yeah, I started by creating a POM but the organization of the code in a grails project doesn't follow the src/target convention.  Like I mentioned, the next stop was the Grails Maven Plugin, but I really didn't need all that functionality.  Grails builds a war just fine, all I needed was to deploy to nexus.

See you next week</description>
		<content:encoded><![CDATA[<p>Yeah, I started by creating a POM but the organization of the code in a grails project doesn&#8217;t follow the src/target convention.  Like I mentioned, the next stop was the Grails Maven Plugin, but I really didn&#8217;t need all that functionality.  Grails builds a war just fine, all I needed was to deploy to nexus.</p>
<p>See you next week</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Stoneham</title>
		<link>http://www.mjwall.com/2009/01/grails-and-maven-with-no-maven/#comment-141</link>
		<dc:creator>John Stoneham</dc:creator>
		<pubDate>Sun, 11 Jan 2009 03:09:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.mjwall.com/?p=89#comment-141</guid>
		<description>There's a lot I don't understand about your setup and why a standard POM/plugin integration won't do the job to create and deploy a WAR. My experience with Maven says the further you get away from tying things to its basic lifecycle the harder you make things.

Looking forward to getting to understand this more closely next week.</description>
		<content:encoded><![CDATA[<p>There&#8217;s a lot I don&#8217;t understand about your setup and why a standard POM/plugin integration won&#8217;t do the job to create and deploy a WAR. My experience with Maven says the further you get away from tying things to its basic lifecycle the harder you make things.</p>
<p>Looking forward to getting to understand this more closely next week.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
