<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments for Test Early</title>
	<link>http://www.testearly.com</link>
	<description>Thought Leaders in helping development teams optimizing Agile software production</description>
	<pubDate>Thu, 07 Aug 2008 19:44:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>Comment on Visual Documentation of Ant Dependencies in 3 Simple Steps by Test Early &#187; NetBeans 6.5 M1 - The Good, The Bad, &#38; The Ugly</title>
		<link>http://www.testearly.com/2008/07/25/visual-documentation-of-ant-dependencies-in-3-simple-steps/#comment-38996</link>
		<pubDate>Mon, 04 Aug 2008 18:52:52 +0000</pubDate>
		<guid>http://www.testearly.com/2008/07/25/visual-documentation-of-ant-dependencies-in-3-simple-steps/#comment-38996</guid>
					<description>[...] I said a lot of things that are good and that need some improvement, so you may ask what is it that I find so ugly within the IDE. If you are writing enterprise Java application, in many cases Ant stands as the universal build platform. NetBeans by default creates all the build files for compiling, testing, deploying, undeploying and running your application. However, even after using Ant for several years now, I had serious trouble using these build files. I did use a tool called Grand and Vizant to generate visual documentation of the build files to understand them better and here is what I was able to get from them. The build files need heavy refactoring for anyone to continue to use within their enterprise applications. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I said a lot of things that are good and that need some improvement, so you may ask what is it that I find so ugly within the IDE. If you are writing enterprise Java application, in many cases Ant stands as the universal build platform. NetBeans by default creates all the build files for compiling, testing, deploying, undeploying and running your application. However, even after using Ant for several years now, I had serious trouble using these build files. I did use a tool called Grand and Vizant to generate visual documentation of the build files to understand them better and here is what I was able to get from them. The build files need heavy refactoring for anyone to continue to use within their enterprise applications. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on 10 Bad Build Practices - Part I by Toby</title>
		<link>http://www.testearly.com/2006/07/20/10-bad-build-practices-part-i/#comment-38975</link>
		<pubDate>Mon, 04 Aug 2008 16:10:58 +0000</pubDate>
		<guid>http://www.testearly.com/2006/07/20/10-bad-build-practices-part-i/#comment-38975</guid>
					<description>I agree and disagree with bad practice one. Setting a base directory is a very very good idea but over parameterisation can make the value unreadable. You then have to look up each parameter and construct the whole.
eg:


If the parameter is only used one then there is little point in making it a parameter. I also think that if it doesn't change much it is better to have a readable build file than a flexible one.
I have also seen pointless parameterisation 
eg
SOURCE=source
or my fav
WEBINF=WEB-INF
Like the java standard is going to change sometime soon</description>
		<content:encoded><![CDATA[<p>I agree and disagree with bad practice one. Setting a base directory is a very very good idea but over parameterisation can make the value unreadable. You then have to look up each parameter and construct the whole.<br />
eg:</p>
<p>If the parameter is only used one then there is little point in making it a parameter. I also think that if it doesn&#8217;t change much it is better to have a readable build file than a flexible one.<br />
I have also seen pointless parameterisation<br />
eg<br />
SOURCE=source<br />
or my fav<br />
WEBINF=WEB-INF<br />
Like the java standard is going to change sometime soon
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Grails vs. Rails - First Impressions by Josh Nichols</title>
		<link>http://www.testearly.com/2008/07/23/grails-vs-rails-first-impressions/#comment-38663</link>
		<pubDate>Sat, 02 Aug 2008 15:32:14 +0000</pubDate>
		<guid>http://www.testearly.com/2008/07/23/grails-vs-rails-first-impressions/#comment-38663</guid>
					<description>Instead of firing up MySQL to see what fields a class has, you can look at db/schema.rb. It's basically a sum of all the migrations you have run.

Also, you could take a look at the annotate_models plugin, which will add comments to your model with the fields and whatnot.

http://agilewebdevelopment.com/plugins/annotate_models</description>
		<content:encoded><![CDATA[<p>Instead of firing up MySQL to see what fields a class has, you can look at db/schema.rb. It&#8217;s basically a sum of all the migrations you have run.</p>
<p>Also, you could take a look at the annotate_models plugin, which will add comments to your model with the fields and whatnot.</p>
<p><a href='http://agilewebdevelopment.com/plugins/annotate_models' rel='nofollow'>http://agilewebdevelopment.com/plugins/annotate_models</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Staged builds with CruiseControl by Timo Meinen</title>
		<link>http://www.testearly.com/2007/04/25/staged-builds-with-cruisecontrol/#comment-38478</link>
		<pubDate>Fri, 01 Aug 2008 09:58:59 +0000</pubDate>
		<guid>http://www.testearly.com/2007/04/25/staged-builds-with-cruisecontrol/#comment-38478</guid>
					<description>Thank you for the dependency-tip. We will try this, too. Small hint: As Subversion uses atomic commits, the quietperiod should be set to 0 as supposed by the cruisecontrol manual.

Best regards,
Timo</description>
		<content:encoded><![CDATA[<p>Thank you for the dependency-tip. We will try this, too. Small hint: As Subversion uses atomic commits, the quietperiod should be set to 0 as supposed by the cruisecontrol manual.</p>
<p>Best regards,<br />
Timo
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on RESTful Web Services in 60 Seconds by meera.subbarao</title>
		<link>http://www.testearly.com/2008/07/23/restful-web-services-in-60-seconds/#comment-37904</link>
		<pubDate>Sat, 26 Jul 2008 14:06:47 +0000</pubDate>
		<guid>http://www.testearly.com/2008/07/23/restful-web-services-in-60-seconds/#comment-37904</guid>
					<description>Hi Josh,
Thanks for the same. It was a typo while writing this post.</description>
		<content:encoded><![CDATA[<p>Hi Josh,<br />
Thanks for the same. It was a typo while writing this post.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on RESTful Web Services in 60 Seconds by Josh Juneau</title>
		<link>http://www.testearly.com/2008/07/23/restful-web-services-in-60-seconds/#comment-37848</link>
		<pubDate>Sat, 26 Jul 2008 05:12:54 +0000</pubDate>
		<guid>http://www.testearly.com/2008/07/23/restful-web-services-in-60-seconds/#comment-37848</guid>
					<description>Great tutorial.  I caught one exception though...you need to add the parentheses to the sayHello method declaration or else the example will not work.

Tested and verified with 6.5 M1 and the latest build as of 7/26/2008.</description>
		<content:encoded><![CDATA[<p>Great tutorial.  I caught one exception though&#8230;you need to add the parentheses to the sayHello method declaration or else the example will not work.</p>
<p>Tested and verified with 6.5 M1 and the latest build as of 7/26/2008.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Grails development made even simpler using NetBeans IDE 6.5 by Cliff</title>
		<link>http://www.testearly.com/2008/07/21/grails-development-made-even-simpler-using-netbeans-ide-65/#comment-37713</link>
		<pubDate>Thu, 24 Jul 2008 22:47:42 +0000</pubDate>
		<guid>http://www.testearly.com/2008/07/21/grails-development-made-even-simpler-using-netbeans-ide-65/#comment-37713</guid>
					<description>IntelliJ's Groovy and Grails is slick, but IntelliJ isn't free...

The new NetBeans blows away any GoG options you had with Eclipse.

Merlyn might be referring to the fact that the Grails plugin was available in previous NetBeans dev builds.  To finally see it on the roadmap for RC inclusion is awesome.  It is also way more stable in 6.5M1 than in previous versions.</description>
		<content:encoded><![CDATA[<p>IntelliJ&#8217;s Groovy and Grails is slick, but IntelliJ isn&#8217;t free&#8230;</p>
<p>The new NetBeans blows away any GoG options you had with Eclipse.</p>
<p>Merlyn might be referring to the fact that the Grails plugin was available in previous NetBeans dev builds.  To finally see it on the roadmap for RC inclusion is awesome.  It is also way more stable in 6.5M1 than in previous versions.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on RESTful Web Services in 60 Seconds by roScripts &#45; Webmaster resources and websites</title>
		<link>http://www.testearly.com/2008/07/23/restful-web-services-in-60-seconds/#comment-37701</link>
		<pubDate>Thu, 24 Jul 2008 18:15:06 +0000</pubDate>
		<guid>http://www.testearly.com/2008/07/23/restful-web-services-in-60-seconds/#comment-37701</guid>
					<description>&lt;strong&gt;Test Early &amp;#xBB; RESTful Web Services in 60 Seconds...&lt;/strong&gt;

Test Early &amp;#xBB; RESTful Web Services in 60 Seconds...</description>
		<content:encoded><![CDATA[<p><strong>Test Early &#xBB; RESTful Web Services in 60 Seconds&#8230;</strong></p>
<p>Test Early &#xBB; RESTful Web Services in 60 Seconds&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Grails development made even simpler using NetBeans IDE 6.5 by meera.subbarao</title>
		<link>http://www.testearly.com/2008/07/21/grails-development-made-even-simpler-using-netbeans-ide-65/#comment-37636</link>
		<pubDate>Wed, 23 Jul 2008 20:56:06 +0000</pubDate>
		<guid>http://www.testearly.com/2008/07/21/grails-development-made-even-simpler-using-netbeans-ide-65/#comment-37636</guid>
					<description>Jesse - I sure will look at IntelliJ IDEA 7. 

Merlyn Albery-Spreyer -  I am a big fan of automation, and don't enjoy working with command prompts or terminals. I like to do everything from within my IDE, and that's what NetBeans allows me to do.</description>
		<content:encoded><![CDATA[<p>Jesse - I sure will look at IntelliJ IDEA 7. </p>
<p>Merlyn Albery-Spreyer -  I am a big fan of automation, and don&#8217;t enjoy working with command prompts or terminals. I like to do everything from within my IDE, and that&#8217;s what NetBeans allows me to do.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Grails development made even simpler using NetBeans IDE 6.5 by Test Early &#187; RESTful Web Services in 60 Seconds</title>
		<link>http://www.testearly.com/2008/07/21/grails-development-made-even-simpler-using-netbeans-ide-65/#comment-37612</link>
		<pubDate>Wed, 23 Jul 2008 15:21:16 +0000</pubDate>
		<guid>http://www.testearly.com/2008/07/21/grails-development-made-even-simpler-using-netbeans-ide-65/#comment-37612</guid>
					<description>[...] Is this even possible? Yes, trust me, if I can do it, so can you. You may ask, from Groovy and Grails in one day, how did I shift gears to web services. It all started while I was reading and working the samples from chapter 9 Web Services of &amp;#8220;Beginning Groovy and Grails from Novice to Professional&amp;#8220;. With the help of the sample provided in the book, I was able to get a RESTful web services for the Grails application. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Is this even possible? Yes, trust me, if I can do it, so can you. You may ask, from Groovy and Grails in one day, how did I shift gears to web services. It all started while I was reading and working the samples from chapter 9 Web Services of &#8220;Beginning Groovy and Grails from Novice to Professional&#8220;. With the help of the sample provided in the book, I was able to get a RESTful web services for the Grails application. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
