Random Java errors that don't make sense

[TubaMorg]

Netbeans automatic error detection can get confused sometimes. Often closing a project and Netbeans, then reopening it will help. But it sounds as if you've already done it. You say it compiles fine? But it still shows errors? Another thing to check is to make sure the project library paths and Java version are set correctly. Sometimes updates will mess those up.
Also try "clean and build". You said you reinstalled Netbeans, did you redo the update too?

Another thing to do that might work is to start a new FIRST project and move your old files to the new project and rebuild.

[1168Programmer]

NetBeans and all the plugins are the newest versions, as far as I can tell. I tried a clean/build and the "errors" are still there, but it compiled fine. Tried making a new project, which had "errors" from the moment I opened it. I think you're right about the library paths. However, there does not appear to be a way to change them through the "projects" tab. However, that does not mean there isn't a way to change them...

?

[inkspell4]

1 have you imported the required/neccicery wpi files
2 have you declared them
3 are caps in places where they shouldnt be
if else recheck/reprogram a similar program and post the differance as they may be of help to others

[1168Programmer]

1. Yes - netbeans is saying all the imports are errors even though they aren't
2. Yes - netbeans thinks the declarations are errors too
3. No

The program was perfectly fine before the updates. Then we updated. Then netbeans got angry.

As of right now, I have uninstalled and reinstalled netbeans and the FIRST plugins twice on our main laptop. I am installing netbeans on our older laptop (so old I needed to install the JDK because it didn't even have one) to test whether our laptop is screwed up or whether our code is.

If/when I figure out what's wrong, I'll post that too. In the meantime any other suggestions are more than welcome.

[1168Programmer]

Ok, netbeans now works on our really old laptop and the project is fine. No "errors". Which is fine, but it doesn't actually solve the problem on the main one.... but of course it could always be that our main laptop is pretty messed up.