<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Eclipse &#8211; Henry Poon&#039;s Blog</title>
	<atom:link href="https://blog.henrypoon.com/blog/tag/eclipse/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.henrypoon.com</link>
	<description></description>
	<lastBuildDate>Sun, 25 Aug 2019 17:48:52 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
<site xmlns="com-wordpress:feed-additions:1">83044199</site>	<item>
		<title>Groovy/Grails unable to resolve class &#8211; even if the class is in the same package</title>
		<link>https://blog.henrypoon.com/blog/2015/01/26/groovygrails-unable-to-resolve-class-even-if-the-class-is-in-the-same-package/</link>
					<comments>https://blog.henrypoon.com/blog/2015/01/26/groovygrails-unable-to-resolve-class-even-if-the-class-is-in-the-same-package/#respond</comments>
		
		<dc:creator><![CDATA[hp]]></dc:creator>
		<pubDate>Tue, 27 Jan 2015 06:44:33 +0000</pubDate>
				<category><![CDATA[gaming]]></category>
		<category><![CDATA[Apache Groovy]]></category>
		<category><![CDATA[Chan]]></category>
		<category><![CDATA[COM]]></category>
		<category><![CDATA[Computing]]></category>
		<category><![CDATA[Cross-platform software]]></category>
		<category><![CDATA[D]]></category>
		<category><![CDATA[Digital technology]]></category>
		<category><![CDATA[EAR]]></category>
		<category><![CDATA[Eclipse]]></category>
		<category><![CDATA[Go]]></category>
		<category><![CDATA[Grails]]></category>
		<category><![CDATA[groovy]]></category>
		<category><![CDATA[IDE]]></category>
		<category><![CDATA[IME]]></category>
		<category><![CDATA[Integrated development environments]]></category>
		<category><![CDATA[ise]]></category>
		<category><![CDATA[It]]></category>
		<category><![CDATA[Java platform]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Time]]></category>
		<category><![CDATA[Writing]]></category>
		<guid isPermaLink="false">https://www.henrypoon.com/blog/?p=2019</guid>

					<description><![CDATA[The Problem Every now and then I get this annoying problem in GGTS (Grails/Groovy Tool Suite &#8211; Version 3.6.2.RELEASE at the time of this writing), where the IDE just complains about how it can&#8217;t resolve a class. &#160;The weird thing is that the file that the IDE is complaining about is in the same package [&#8230;]]]></description>
										<content:encoded><![CDATA[<h1>The Problem</h1>
<p>Every now and then I get this annoying problem in GGTS (Grails/Groovy Tool Suite &#8211; Version 3.6.2.RELEASE at the time of this writing), where the IDE just complains about how it can&#8217;t resolve a class. &nbsp;The weird thing is that the file that the IDE is complaining about is in the same package as the class that I&#8217;m trying to use. &nbsp;It built before, and the source hadn&#8217;t changed &#8211; so clearly this should not be happening.</p>
<h1>The Fix</h1>
<p>Hitting the Clean button on the Eclipse side (Project -&gt; Clean) seems to make the errors go away.</p>
<p>This apparently has been a problem since June 2010 (forum post reference <a href="http://forum.spring.io/forum/spring-projects/springsource-tool-suite/83417-groovy-unable-to-resolve-class-although-same-package-again" target="_blank" rel="noopener noreferrer">here</a>), so I&#8217;m surprised that it is still an issue in the current version.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.henrypoon.com/blog/2015/01/26/groovygrails-unable-to-resolve-class-even-if-the-class-is-in-the-same-package/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2019</post-id>	</item>
	</channel>
</rss>
