bootstrap class path errors

Newbie & Debugging Questions
#1

Ok while building my java game, everything appeared fine until I ran it and my engine caught a IO exception, after checking over the code trying to figure out what could have caused this, I checked the build log and came across these notes/errors:

warning: [options] bootstrap class path not set in conjunction with -source 1.6
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

could these compile errors/notes have something to do with this and if not, what could (i know it’s a big question) be causing these errors?

#2

The first warning you can usually ignore – it means you might possibly be using 1.7 APIs in your code that you’re generating for 1.6, and that you’d prevent that by setting the bootstrap class path to 1.6. If all you have is 1.7, you’re going to get that.

As for the other two, have you considered doing what the message says and adding -Xlint:deprecation to your compiler flags? Open your IDE preferences, search for “deprec”, look for a checkbox to enable deprecation warnings.

#3

I’ll try that, I had no idea how to do that :stuck_out_tongue:

#4

hey could you tell me where to find that in NetBeans, I’m such a noob :expressionless:

#5

Don’t know, I don’t use Netbeans. You might have to paste it in to a text field or something.

#6

Netbeans should be crossing out the deprecated variables/methods that you might be using.

IOExceptions however have no relations to deprecated stuff at all :wink:

#7

So will the culprits be literally crossed out in the code editor, i.e. if I look through will I find them?

#8

yep, it should also be possible to just click on the warnings in the compiler output in the IDE

#9

cheers, thanks for your patience guys, I know I must seem like an absolute idiot in comparison to you guys, but hey I guess this is what happens when you teach yourself! :stuck_out_tongue: