<?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: More info on JSP support for Eclipse</title>
	<atom:link href="http://www.digitalhobbit.com/archives/2004/11/07/more-info-on-jsp-support-for-eclipse/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.digitalhobbit.com/archives/2004/11/07/more-info-on-jsp-support-for-eclipse/</link>
	<description>Thoughts from the hobbit hole</description>
	<pubDate>Wed, 07 Jan 2009 08:51:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: DigitalHobbit</title>
		<link>http://www.digitalhobbit.com/archives/2004/11/07/more-info-on-jsp-support-for-eclipse/#comment-33</link>
		<dc:creator>DigitalHobbit</dc:creator>
		<pubDate>Thu, 18 Nov 2004 06:06:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalhobbit.com/blog/archives/2004/11/07/more-info-on-jsp-support-for-eclipse/#comment-33</guid>
		<description>Eclipse is definitely a very decent tool, I agree - even though there are still a few rough edges. I wonder how close WSAD's JSP support is to IBM's contribution to the Eclipse Web Tools Platform project. I assume that this must be the origin of the code, which would be promising. I have removed the milestone release of the WTP from my Eclipse installation, but I have yet to try running IBM's contribution. One of these days...</description>
		<content:encoded><![CDATA[<p>Eclipse is definitely a very decent tool, I agree - even though there are still a few rough edges. I wonder how close WSAD&#8217;s JSP support is to IBM&#8217;s contribution to the Eclipse Web Tools Platform project. I assume that this must be the origin of the code, which would be promising. I have removed the milestone release of the WTP from my Eclipse installation, but I have yet to try running IBM&#8217;s contribution. One of these days&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken</title>
		<link>http://www.digitalhobbit.com/archives/2004/11/07/more-info-on-jsp-support-for-eclipse/#comment-32</link>
		<dc:creator>Ken</dc:creator>
		<pubDate>Thu, 18 Nov 2004 02:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalhobbit.com/blog/archives/2004/11/07/more-info-on-jsp-support-for-eclipse/#comment-32</guid>
		<description>I work pretty much everyday with the WebSphere Studio Application Developer (WSAD) the PAY version of the Eclipse equation. It's got great support for jsp editing, comparatively speaking. I run WSAD at work and Eclipse at home, and the free Eclipse is a poor cousin in comparison. However, there are many different pieces/parts you can use with Eclipse which is the great thing. If you REALLY want to have highlighting and such, write your own plugin for Eclipse and call it a day. 

As for Ant in Eclipse, I think it's ok, but I still mandate that my developers 'do it raw'. Meaning that they complete build still must function correctly (including junit, jcoverage, checkstyle, jdepend, etc, etc,etc, all other steps). I have found problems getting all the Ant stuff to work correctly with WSAD as it adds some funky classpath issues that have to be resolved, that and it has some internal 'gotchas' in the classpath also (like it's own version of xerces hidden in the bowels of the system). 

No tool is perfect, but for free, it's worth more than most I've seen out there.</description>
		<content:encoded><![CDATA[<p>I work pretty much everyday with the WebSphere Studio Application Developer (WSAD) the PAY version of the Eclipse equation. It&#8217;s got great support for jsp editing, comparatively speaking. I run WSAD at work and Eclipse at home, and the free Eclipse is a poor cousin in comparison. However, there are many different pieces/parts you can use with Eclipse which is the great thing. If you REALLY want to have highlighting and such, write your own plugin for Eclipse and call it a day. </p>
<p>As for Ant in Eclipse, I think it&#8217;s ok, but I still mandate that my developers &#8216;do it raw&#8217;. Meaning that they complete build still must function correctly (including junit, jcoverage, checkstyle, jdepend, etc, etc,etc, all other steps). I have found problems getting all the Ant stuff to work correctly with WSAD as it adds some funky classpath issues that have to be resolved, that and it has some internal &#8216;gotchas&#8217; in the classpath also (like it&#8217;s own version of xerces hidden in the bowels of the system). </p>
<p>No tool is perfect, but for free, it&#8217;s worth more than most I&#8217;ve seen out there.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
