<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Grails build-test-data presentation</title>
	<atom:link href="http://naleid.com/blog/2009/07/14/grails-build-test-data-presentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://naleid.com/blog/2009/07/14/grails-build-test-data-presentation/</link>
	<description>Groovy, Grails and OS X tips and tricks</description>
	<lastBuildDate>Sat, 31 Jul 2010 11:43:17 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Grails build-test-data plugin version 1.0 released - Ted Naleid</title>
		<link>http://naleid.com/blog/2009/07/14/grails-build-test-data-presentation/comment-page-1/#comment-2599</link>
		<dc:creator>Grails build-test-data plugin version 1.0 released - Ted Naleid</dc:creator>
		<pubDate>Thu, 18 Mar 2010 04:48:57 +0000</pubDate>
		<guid isPermaLink="false">http://naleid.com/blog/?p=59#comment-2599</guid>
		<description>[...] with the build-test-data plugin, the documentation on the wiki is thorough, I&#8217;ve also given a presentation on build-test-data that explains why it&#8217;s better than other existing data generation [...]</description>
		<content:encoded><![CDATA[<p>[...] with the build-test-data plugin, the documentation on the wiki is thorough, I&#8217;ve also given a presentation on build-test-data that explains why it&#8217;s better than other existing data generation [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://naleid.com/blog/2009/07/14/grails-build-test-data-presentation/comment-page-1/#comment-1941</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Sat, 29 Aug 2009 13:03:06 +0000</pubDate>
		<guid isPermaLink="false">http://naleid.com/blog/?p=59#comment-1941</guid>
		<description>Thanks for this plugin.</description>
		<content:encoded><![CDATA[<p>Thanks for this plugin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted Naleid &#187; Grails build-test-data plugin version 0.2.3 released</title>
		<link>http://naleid.com/blog/2009/07/14/grails-build-test-data-presentation/comment-page-1/#comment-1907</link>
		<dc:creator>Ted Naleid &#187; Grails build-test-data plugin version 0.2.3 released</dc:creator>
		<pubDate>Wed, 26 Aug 2009 00:39:34 +0000</pubDate>
		<guid isPermaLink="false">http://naleid.com/blog/?p=59#comment-1907</guid>
		<description>[...] Build-Test-Data Presentation [...]</description>
		<content:encoded><![CDATA[<p>[...] Build-Test-Data Presentation [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yuval</title>
		<link>http://naleid.com/blog/2009/07/14/grails-build-test-data-presentation/comment-page-1/#comment-1834</link>
		<dc:creator>Yuval</dc:creator>
		<pubDate>Thu, 20 Aug 2009 14:49:34 +0000</pubDate>
		<guid isPermaLink="false">http://naleid.com/blog/?p=59#comment-1834</guid>
		<description>Great plugin, it&#039;s saves so much time!

 keep up the good work.</description>
		<content:encoded><![CDATA[<p>Great plugin, it&#8217;s saves so much time!</p>
<p> keep up the good work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tednaleid</title>
		<link>http://naleid.com/blog/2009/07/14/grails-build-test-data-presentation/comment-page-1/#comment-1641</link>
		<dc:creator>tednaleid</dc:creator>
		<pubDate>Fri, 17 Jul 2009 17:35:14 +0000</pubDate>
		<guid isPermaLink="false">http://naleid.com/blog/?p=59#comment-1641</guid>
		<description>@Roshan by default, when the plugin is installed, it&#039;s enabled in all environments.  This is because there are reasons why you might legitimately want to call build outside of a unit test (ex: if you connect a grails console and want to create some objects to play with, or in your BootStrap script to get some sample objects in the DB).

if you&#039;re not using the build() method in production but you leave the plugin enabled, the only performance impact would be the time it takes for the metaclass to get decorated with the build() method on startup.  (i.e. less than a second to startup time).  Once the app is running, there would be no impact.

It&#039;s absolutely safe to have the plugin running in production, but the option to turn it off is there for people who want to make sure that their users aren&#039;t calling build() in production code.</description>
		<content:encoded><![CDATA[<p>@Roshan by default, when the plugin is installed, it&#8217;s enabled in all environments.  This is because there are reasons why you might legitimately want to call build outside of a unit test (ex: if you connect a grails console and want to create some objects to play with, or in your BootStrap script to get some sample objects in the DB).</p>
<p>if you&#8217;re not using the build() method in production but you leave the plugin enabled, the only performance impact would be the time it takes for the metaclass to get decorated with the build() method on startup.  (i.e. less than a second to startup time).  Once the app is running, there would be no impact.</p>
<p>It&#8217;s absolutely safe to have the plugin running in production, but the option to turn it off is there for people who want to make sure that their users aren&#8217;t calling build() in production code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roshan Shrestha</title>
		<link>http://naleid.com/blog/2009/07/14/grails-build-test-data-presentation/comment-page-1/#comment-1639</link>
		<dc:creator>Roshan Shrestha</dc:creator>
		<pubDate>Fri, 17 Jul 2009 16:06:51 +0000</pubDate>
		<guid isPermaLink="false">http://naleid.com/blog/?p=59#comment-1639</guid>
		<description>Does the plugin affect the deployment of the application in any way (such as performance, etc). I think it adds a number of methods to the domain objects, but these are not required for the deployed classes. Are these methods added only for the development build?

Thanks for the excellent plugin.</description>
		<content:encoded><![CDATA[<p>Does the plugin affect the deployment of the application in any way (such as performance, etc). I think it adds a number of methods to the domain objects, but these are not required for the deployed classes. Are these methods added only for the development build?</p>
<p>Thanks for the excellent plugin.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
