<?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: Should every target have a secret?</title>
	<atom:link href="http://www.build-doctor.com/2008/07/16/should-every-target-have-a-secret/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.build-doctor.com/2008/07/16/should-every-target-have-a-secret/</link>
	<description>Helping to deliver working software, one continuous integration build at a time</description>
	<lastBuildDate>Wed, 21 Jul 2010 04:50:11 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Julian</title>
		<link>http://www.build-doctor.com/2008/07/16/should-every-target-have-a-secret/comment-page-1/#comment-183</link>
		<dc:creator>Julian</dc:creator>
		<pubDate>Mon, 21 Jul 2008 21:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://beta.build-doctor.com/?p=71#comment-183</guid>
		<description>Eric, I know what you mean.  I&#039;m not against Maven but I never thought that it was appropriate for any of my projects.  Once of these days I&#039;ll have to have a proper look.  I think it&#039;s still the only build solution that will easily trigger a CruiseControl build when dependencies change.</description>
		<content:encoded><![CDATA[<p>Eric, I know what you mean.  I&#8217;m not against Maven but I never thought that it was appropriate for any of my projects.  Once of these days I&#8217;ll have to have a proper look.  I think it&#8217;s still the only build solution that will easily trigger a CruiseControl build when dependencies change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Lefevre</title>
		<link>http://www.build-doctor.com/2008/07/16/should-every-target-have-a-secret/comment-page-1/#comment-182</link>
		<dc:creator>Eric Lefevre</dc:creator>
		<pubDate>Fri, 18 Jul 2008 07:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://beta.build-doctor.com/?p=71#comment-182</guid>
		<description>Yes, I think you are making an excellent point.&lt;br/&gt;That said, I&#039;d balanced it with the fact that you sometimes need &#039;technical targets&#039; for which you would need technically explicit names, just like private methods.&lt;br/&gt;&lt;br/&gt;Of course, the limitation is that you cannot easily hide those technical targets from the reader/user of your Ant targets.&lt;br/&gt;&lt;br/&gt;I know you are not a bug fan of Maven, but that seems to be something they got mostly right.</description>
		<content:encoded><![CDATA[<p>Yes, I think you are making an excellent point.<br />That said, I&#8217;d balanced it with the fact that you sometimes need &#8216;technical targets&#8217; for which you would need technically explicit names, just like private methods.</p>
<p>Of course, the limitation is that you cannot easily hide those technical targets from the reader/user of your Ant targets.</p>
<p>I know you are not a bug fan of Maven, but that seems to be something they got mostly right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey Fredrick</title>
		<link>http://www.build-doctor.com/2008/07/16/should-every-target-have-a-secret/comment-page-1/#comment-181</link>
		<dc:creator>Jeffrey Fredrick</dc:creator>
		<pubDate>Thu, 17 Jul 2008 15:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://beta.build-doctor.com/?p=71#comment-181</guid>
		<description>Great post Julian!&lt;br/&gt;&lt;br/&gt;I&#039;m usually trying to convince people that &quot;tests are code&quot; and need to be treated with as much care when it comes to design, refactoring, maintainability, etc.&lt;br/&gt;&lt;br/&gt;Couldn&#039;t agree more that &quot;builds are code&quot; is just as true.</description>
		<content:encoded><![CDATA[<p>Great post Julian!</p>
<p>I&#8217;m usually trying to convince people that &#8220;tests are code&#8221; and need to be treated with as much care when it comes to design, refactoring, maintainability, etc.</p>
<p>Couldn&#8217;t agree more that &#8220;builds are code&#8221; is just as true.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
