We Keep Coding

Netbeans stuck at startup

I was working with a big project on Netbeans.
I attached some source code on third party library and all went smooth.
Today I have the following popup message (I already had seen before obviously):
The file [...] cannot be safely opened with encoding windows-1252. Do you want to continue opening it?
The two buttons, yes and no, are not responsive. If I close the popup with the red cross it does nothing after a 1 sec loading.
Is there a way to "clean" the open file in the netbeans workspace to avoid this error?
SO Windows 8.1, Netbeans 8.0.2
Thanks.

One general solution to this kind of problem can be to clear the netbeans cache.
Quit NetBeans and find the cache folder - mine is at C:\Users\OldCurmudgeon\AppData\Local\NetBeans\Cache. Delete the whole folder - this can take a while as there can be a lot of files in there.
Netbeans will create a new one on next start.
Note that this will slow down netbeans for a while but it won't be long before it is back up to speed again.

Quit NetBeans.
go to the last Project folder then remove the project from the folder.
Open NetBeans.

I had a similar situation which started happening after I added a new project yesterday. I deleted the cache as someone recommended, but was still having the same issue. The solution was to rename the new project so it wouldn't be found. Everything worked splendidly after that.

The import cannot be resolved in eclipse [duplicate]

This question already has answers here:
Eclipse error: "The import XXX cannot be resolved"
(47 answers)
Closed 6 years ago.
Though I have all my source in proper packages.It couldn't find at the time of Building Project.Normally it shows links everything.But at the time of Build Project or Autobuild while directly running project.
The import ecnet.rd.config cannot be resolved
like it shows for all the internal imports.But external imports like imports from JAR files are working.
P.S :
My Eclipse latestly crashed but it was working well after that, Once again this kind of things are happening.
Please help to find the way to solve this.

In my experience, it is usual with Eclipse to have the build messed up. Make sure Build automatically is checked and Clean. If it doesn't work, restart Eclipse and do again.
Also as Tech Junkie comments below, try also Clean all projects.

I've seen this happen and another approach to take which is similar to m0skit0 solution (if you are using Eclipse) is to right click on the project, select maven, select update project, make sure clean projects and refresh workspace are checked, and hit ok.

After hours of struggle, creating a new Eclipse workspace, reimporting the projects and resetting up the same tomcat instance worked.
Probably the eclipse settings got messed up, and the deploy wasn't being done correctly anymore.

Newly Created Android Application Project missing R.java file [duplicate]

This question already has answers here:
Another R.Java file missing [duplicate]
(5 answers)
Closed 9 years ago.
I opened an android application project called Test Canvas and later cleaned it by
Project > Clean ...
'Bulid Automatically' option was ticked.
Then the R.java file was deleted and it did not regenerated.I tried all the other options mentioned in the questions of stackexchange.But the R.java file remained missing.
One answer said that R.java generation fails because of errors in .xml files.But there were no errors.I'm 100% sure.
Then i created a new android application project which cannot have any issues in xml files.
When i created the new project it didn't came with the R.java file. I tried cleaning and building with different combinations.It still doesn't work.
I am using eclipse Helios
Android API 15
Android SDK Manager Revision 22
JDK 7U25
Can any one help me on this please?

I understand you have tried cleaning the project. What I would like you to do is Build the project and check the console for any errors.
The R.java also doesn't gets generated if the your project contains errors and these errors are clearly mentioned in your console.
Have a look and see if you can resolve your problem.

Try the following
Close and Reopen the project
Ensure your project folder has 777 rights
Use a later version of Android, that triggers a clean build
Check Problems tab, sometimes errors are not shown on the project files/folder, but a error shows up in this tab
Check top to see the amount of memory you have left, sometimes OOM screws things up
Please use a more later version 1.5 is like decades old

Try this.
Open the properties of your Project
Go to the Android Build target of your Application
Just change the from the currently checked one to another version(can be anything, but one that is supported to at least the minSDK declared in the Manifest)
Do a clean build, if your Project has no issues like in your resources like hyphens in draw able names,unrecognized strings,missing dimension values etc ... your Project should generate the R package with the R class

R.java not generated after ADT update [duplicate]

This question already has answers here:
Class not found error after updating ADT and Android sdk tools to latest ver 22
(1 answer)
Eclipse giving error, missing R.java file after recent update
(14 answers)
Closed 9 years ago.
I update my android tools and also my ADT. I cleaned my project and build it again. However after this action my /gen folder is empty.
I have made sure that none of my resource contains errors and also made sure that there is no import.R in my activity. I tried cleaning and rebuilding other projects as well with same error. I created a new android project and even the new project had and empty /gen folder.
Solved:
After the update you need to restart the SDK manager and download android build tools. After i clean my projects everything is fine again. Thank you guys.

Yesterday I had the same problem.
That's what I did:
Upgrade Android Development Tools to v.22
How?
Tab Help -> Install new SW using this site: https://dl-ssl.google.com/android/eclipse

Are you referencing the correct android SDK location, and do you have the necessary platforms/api level that you are referencing in your project?

Did you try moving project folders to a different location, e.g. to your documents or another drive?
The errors with the build path can be fixed by clicking Android Tools->Fix Project Properties
EDIT :
1) Make sure you don't have any other errors other than the R-related errors. Right-click your project folder in Eclipse, Android Tools -> Fix Project Properties.
do this
2) Check to make sure you have the correct R imported. Sometimes the default Android.R can be imported.
3) Check for errors in your layout XML files.

check in your sdk manager whether the android platform tools is installed , check whether the api you are targetting is installed and also in eclipse File-properties-builders check if everthing is selected. if all this is fine then if you have not restated your system after update then restart it.

Eclipse - Generated file not appearing in project folder [duplicate]

This question already has answers here:
Closed 11 years ago.
Possible Duplicate:
Auto refresh eclipse project upon folder update
I have been working with Java projects using Eclipse (both Ganymede and Helios). I have noticed that when I generate a file, for instance if I create and write data to a text file, or if I serialize some objects, then although the file is visible if I search outside of eclipse (i.e. using windows explorer or the places on linux) it is not appearing in my project folder.
If I try and import this file into my project, then Eclipse tells me that I can't do this because the file is already in my project structure. So I have to move the file manually outside of this folder using windows explorer etc and then import it into the eclipse project before I can see it.
Is there a way to make these generated files appear automatically? What ias the reason they're not already doing so?
Thanks in advance

right click on the project -> refresh
or press F5

Refresh your Eclispe project (F5).

If you are writing those files programmatically, you might be interested in either Auto refresh as Beau suggested, or, if you can, switch to the Eclipse IO API if you wish tighter integration with Eclipse, which will directly take care of this.