Comments for Philip Yurchuk

Comment on Eclipse “cannot be resolved to a type” error by Tynham

Tynham — Tue, 14 Feb 2012 05:57:18 +0000

Ok so I am not sure if you are familiar with minecraft code but I am trying to create a new block and i keep getting an error saying BaseMod can not be resolved to type

Comment on Eclipse “cannot be resolved to a type” error by Fred

Fred — Tue, 31 Jan 2012 09:46:44 +0000

This kind of stuff is the reason i hate programming. I don’t have a problem with logic errors, syntax errors, etc. but Christ’s dusty nuts I hate bureaucracy.

I started with a completely new set up. Wrote a hello world program. It worked fine. Then I tried to use Date(): cannot resolve class. Tried GregorianC…cannot resolve class. Everything: cannot resolve class.

10 minutes into playing with Eclipse and I am searching for obscure error.

Comment on Eclipse “cannot be resolved to a type” error by amir sepasi

amir sepasi — Wed, 25 Jan 2012 22:20:44 +0000

The way it worked for me was to include all .h files that the red underline refer to, compile it clean, and then remove them. Seems that Eclipse has problem to automatically find the path but once does it holds into it.

Comment on Eclipse “cannot be resolved to a type” error by Derval

Derval — Thu, 19 Jan 2012 21:26:06 +0000

Thanks a million for the “project – clean” suggestion. I had the same problem and this solution worked for me. Good times

Comment on Eclipse “cannot be resolved to a type” error by david

david — Mon, 19 Dec 2011 16:27:12 +0000

I have had this problem for a long time with Eclipse Helios. Usually doing a Project Clean and then a project Refresh clears it up. Not today. I do most builds with Ant and that seems to mess it up. I agree it is a bug and a very annoying one.

Comment on Eclipse “cannot be resolved to a type” error by praveen

praveen — Mon, 24 Oct 2011 07:29:58 +0000

still i am getting that error even though i applied all the above tips …. pls help me

Comment on Eclipse “cannot be resolved to a type” error by TanNhu

TanNhu — Mon, 24 Oct 2011 02:59:22 +0000

Thanks a lot, Kamil!
It solved my problem.

Comment on Eclipse “cannot be resolved to a type” error by Abenia

Abenia — Fri, 30 Sep 2011 23:30:55 +0000

This tiresome bug haunted me for abot TWO hours!!!!!
Luckily Closing project, Open Project, Project–>Clean did the trick!!

Comment on Deleting (undeletable) Tasks In Eclipse by sdoca

sdoca — Fri, 23 Sep 2011 15:40:16 +0000

Thanks for this post. Based on the comments, I did a clean/build and to see what that did and it got rid of the markers. I use m2eclipse, so rarely use the Eclipse clean/build anymore and didn’t think to try that. This was using Eclipse Helios SR2.

Comment on Eclipse “cannot be resolved to a type” error by Faraz Hussain

Faraz Hussain — Fri, 23 Sep 2011 02:29:34 +0000

I had a similar problem; the difference was that I use ant in the command line to build, not enclipse (so build automatically is disabled).

As for others, suddenly it started showing “-cannot-be-resolved-to-a-type” errors.

After being stuck for hours; I tried the following (not sure why I did):

select an error in the “problems” tab and delete it. It worked.

So I selected all of them and simply deleted them.

Who would have thought!

(Btw its Eclipse’s unreliability the reason that I build everything from the command line)