<?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: Separation of Ant and NetBeans</title>
	<atom:link href="http://www.fuzzylizard.com/archives/2005/07/14/587/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fuzzylizard.com/archives/2005/07/14/587/</link>
	<description>My thoughts on Agile, Java and Ruby on Rails (mostly)</description>
	<pubDate>Tue, 06 Jan 2009 15:22:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: fuzzylizard</title>
		<link>http://www.fuzzylizard.com/archives/2005/07/14/587/comment-page-1/#comment-600</link>
		<dc:creator>fuzzylizard</dc:creator>
		<pubDate>Sat, 16 Jul 2005 03:00:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/archives/2005/07/14/587/#comment-600</guid>
		<description>I also include the jar files inside of the project directory. In my opinion, this is a best practice. Every Java project should contain a /lib directory that holds all the jar files for that project. I really don't understand the reasoning behind setting up libraries in NetBeans for this or trying to get developers to add the necessary jars to some classpath environment variable.

What made my "project" more complex was that I was trying to orchestrate all of this across 7 projects. And most projects were dependent on at least one other project, sometime upwards of 3 projects.

I am glad to hear you liked the posts and found them helpful. I also enjoy finding a post somewhere where another developer is talking about a problem that I am struggling with. At the very least it afirms that you are not the only one.</description>
		<content:encoded><![CDATA[<p>I also include the jar files inside of the project directory. In my opinion, this is a best practice. Every Java project should contain a /lib directory that holds all the jar files for that project. I really don&#8217;t understand the reasoning behind setting up libraries in NetBeans for this or trying to get developers to add the necessary jars to some classpath environment variable.</p>
<p>What made my &#8220;project&#8221; more complex was that I was trying to orchestrate all of this across 7 projects. And most projects were dependent on at least one other project, sometime upwards of 3 projects.</p>
<p>I am glad to hear you liked the posts and found them helpful. I also enjoy finding a post somewhere where another developer is talking about a problem that I am struggling with. At the very least it afirms that you are not the only one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Czepiel</title>
		<link>http://www.fuzzylizard.com/archives/2005/07/14/587/comment-page-1/#comment-599</link>
		<dc:creator>Mike Czepiel</dc:creator>
		<pubDate>Sat, 16 Jul 2005 02:51:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/archives/2005/07/14/587/#comment-599</guid>
		<description>I actually stumbled upon your previous entry as I was trying to solve this very problem myself. Being a newcomer to Netbeans, Ant, and Java Web Development (Coming from a PHP background) this was proving failry difficult.

We thankfully only have a small group of new developers working on this project, so I have no problem mandating Netbeans if nothing more than as a learning tool. In any event I found the easist solution in our case was to ensure the jars we needed were within the project. At that point the paths in the build scripts were relative to project root. Consequently, we've managed to build the site on another system without any modifications to the build scripts.

Perhaps at  some point once we're more comfortable with Ant we'll be able to migrate over to the external build.xml, which arguably sounds liek a better solution. 

So ultimately, just wanted to say it was good following along to see how someboddy else ultimately solved the problem...and to say that I'm surprised there's no easily found "best practice guide" regarding such a seemingly unavoidable hurdle for newcomers and experienced developers alike.</description>
		<content:encoded><![CDATA[<p>I actually stumbled upon your previous entry as I was trying to solve this very problem myself. Being a newcomer to Netbeans, Ant, and Java Web Development (Coming from a PHP background) this was proving failry difficult.</p>
<p>We thankfully only have a small group of new developers working on this project, so I have no problem mandating Netbeans if nothing more than as a learning tool. In any event I found the easist solution in our case was to ensure the jars we needed were within the project. At that point the paths in the build scripts were relative to project root. Consequently, we&#8217;ve managed to build the site on another system without any modifications to the build scripts.</p>
<p>Perhaps at  some point once we&#8217;re more comfortable with Ant we&#8217;ll be able to migrate over to the external build.xml, which arguably sounds liek a better solution. </p>
<p>So ultimately, just wanted to say it was good following along to see how someboddy else ultimately solved the problem&#8230;and to say that I&#8217;m surprised there&#8217;s no easily found &#8220;best practice guide&#8221; regarding such a seemingly unavoidable hurdle for newcomers and experienced developers alike.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
