When trying to install eclipse, when I run the installer I just get a blank box with no packages to select. Image Link
Any idea on how I could fix it, I have my java environment variable and java_home both set to the \bin location for both my java installations. The versions of java I currently am using are jdk 8 and I got jdk 16 to see if that might fix the issue but it didn't. As well, there weren't any errors or anything it just shows the empty box and shows that there's an update but I'm not sure what it's trying to update. Any idea how I could fix it?
Solution that worked for me:
Ok so after some fiddling around I had to search "eclipse" in the search all bar in windows. Then after some scrolling I was able to find the file "eclipse-isnt.exe" and after running that it showed the stuff to download and solved my problem. The "eclipse-isnt.exe" ended up being located in "C:/Users/(user)/AppData/Local/Temp/(random temp file)/eclipse-inst.exe".
Hope this helps out
Also running the file as administrator worked
I am a beginner developer trying to create my first project using Jhipster. I am trying to set up everything to start coding in the most accurate environment in order to avoid further problems or warning in the future.
I have imported the new project to the Eclipse IDE following the instructions in jHipster web, but as you can see in the picture, some warnings appear:
Is there something important that I have to worry about? If yes, how can I solve it?
I can solve the first one, but I am not sure if I solve it in the right way. I did not find any solution related to the other ones.
Is there something important that I have to worry about? If yes, how can I solve it?
Warnings are not high priority problems, they will not break your application. That said fixing them is never a bad idea, I personally like to keep my projects clean.
Most of the Java problems you have are for unused imports or variables, remove them from your code and the warnings will disappear. You can double click on each warning and eclipse will take you right to the line of code.
For the serialVersionUID problems you can just click on the yellow light bulb left of the line number and then click Add default serial version ID.
The first two problems you say you can fix them, good. They are telling you there is a mismatch between the expected Java version and the one used. One way to fix them is to install the 1.8 JDK (get it from here) and set it as your default JRE (Windows > Preferences > Java > Installed JREs).
After upgrading to new eclipse Oxygen (4.7.0), I don't see code warnings or errors when I hover on the highlighted code element.
Also, I can't get variable values in debug mode when hovering on one.
For both cases, javadoc is being show.
I tried to reset hover preferences under Java and general section to its defaults, but it does not fix the problem.
Is there any workaround/fix for this, or as usual, we have to wait for the next eclipse service release?
I'm answering my own question, to help anyone with the same issue.
After reporting this to eclipse Bugzilla, I got a comment about possibility of conflict with an updated plugin. I then checked my newly installed plugins and found the guilty one: ZipEditor v1.1.3.201703012047
Deleting this plugin fixed my issue.
EDIT: It looks like the issue was layered and I had to remove eclipse Class Decompiler 2.9.11.20170710, too.
I've been living with a very annoying problem in Eclipse where if I declare a type that cannot be uniquely resolved, the tooltip that prompts me to choose the correct class sometimes does not display the full link.
As seen in the screenshot here, I have 9 different Version classes in my workspace, and only 3 of them display properly in the tooltip. The other 6 links still work, but I'd have to click on them first to see exactly which one gets imported.
I've had this problem for quite a while now, and updating to the latest Kepler release did not help. Has anyone else seen this problem or any idea how to debug this?
Specs:
Ubuntu x64 13.10
Eclipse 3.7.2 ~ 4.3.1
Anuparna provided the link in the comment which resolves my issue.
*Edit
Solution:
Go to General->Appearence->Colors and Fonts: Basic > Dialog Font and play around with the settings until you find something that works.
I know this question has been asked before and I have seen a plethora of solutions out there, yet none seem to work for me. I was able to build my apk without issues until this error started cropping up. I have tried cleaning my project, removing it from the workspace and reimporting it, removing "Java Builder" from my Builders for the project, building the project manually, reordering my java build path. I have no visible compiler issues and no problems exist in my workspace.
I did experience this issue before and solved it once by removing the project form my workspace and re-importing it and another time I solved it by removing "Java Builder" from my java build path. None seem to work this time. I currently have most of the settings set back to default (i.e. java build is checked again).
I am running windows 7 (64 bit) and using jdk1.6.0_21 via Eclipse 3.6.
Any suggestions would be greatly appreciated as I have lost loads of development time troubleshooting this already.
[Update] My locale is English & I have tried removing the debug.keystore, United States as related to issue 834
Please follow these steps; this might help you out:
Right-click your app project and go to Properties
Select Android from left-hand side list
Uncheck the "Is Library" checkbox
If your app project relies on library projects which are in your workspace, those of course need to have the "Is Library" box checked.
deleting the R.Java file in /Gen folder did the trick for me
I tried all the above solutions. but it didn't work.
The solution was to restart eclipse !!!!!!!
hope this will help someone :)
In my case this problem started after eclipse updated the plugin with the v4.0 API release. I fixed it by going to the main preferences for Eclipse and under Android->Build uncheck 'Skip packaging and dexing until export or launch'
Note: if you eclipse gives you the Unknown Command 'crunch' error then follow this post
I've tried to gather the best of other peoples answers into a step by step list of things to try in order:
Check the project is not set as a library:
Go to Project->Properties
Select Android from left-hand side list
Uncheck the "Is Library" checkbox
Clean and rebuild the project - this should delete and recreate the entire gen folder, including the R.java file mentioned in some peoples answers
Check eclipse and all the Android plugins are up to date
Close the project, exit Eclipse, reopen eclipse, reopen the project.
Go to Java Build Path > Projects and check for any incorrect project dependencies
Go to the main preferences for Eclipse and under Android->Build uncheck 'Skip packaging and dexing until export or launch'
Check JAVA_HOME is set correctly. Follow the steps in this article
If you complete the above list, and still haven't solved the issue, please leave a comment, or if you find something else that works, feel free to edit the answer and add your thing in.
Delete the project from your workspace & import again.
This worked for me.
Can't believe similar issue has been there since 2008.
http://code.google.com/p/android/issues/detail?id=834.
i'm no expert, but eclipse on Windows, doing android apps, refuses to create the default.properties file (in the app root directory). I've just copied one from another app and it works fine. Simple contents, for Android 2.2 project it just says (ignoring comments):
target=android-8
fwiw
I was having the same issue as the OP except that all these suggestions did not work. I found a solution for me.
Make sure that "Skip packaging and dexing until export or launch." is selected.
Go to Window -> Preferences -> Android -> Build. Just make sure that option is selected and apply.
I know this does not make a lot of sense, but having it unselected was giving me this error and with it selected it goes away and the apk is installed.
I am using the auto generated ant build script from android and ONLY using it as my build process in eclipse. I am not using any other build methods.
I figured it out. I was referencing JavaSE-1.5 and using JDK 1.6. I changed it to use 1.6 and that appears to fix it.
Seems like through my research that is an overloaded error message that covers a lot of error cases.
I just fixed this by reselecting a default JRE for the execution environment (JRE6 for JavaSE-1.6 in my case). It got unchecked for some reason.
This fixed my problem. I kept getting the console error in eclipse "Could not find com_android_vending_licensing.apk" and even though it didnt seem to effect the way my app ran, it was annoying. So going into the com_android_vending_licensing project properties and unchecking the "is library" option, building the project to produce the needed apk and then going back into the com_android_vending_licensing project properties and re checking the "is library" check box fixed the problem.
Run Eclipse as "Administrator" and then import the project.
None of these things worked for me. I'm trying to access native code through the jni, first with NDK samples. What I found was the build won't run if jarlist.cache is not present in the project bin directory. If I copy one from another project to that location (may need to refresh to see the folder in Eclipse), build works every time.
Clean the project and it will do. Sometimes it happens unknowingly but keep trying to solve using diff methods.
I had somehow done a Run configuration as a Java application instead of a Android.
the problem for me was I was trying to use IBM RAD which appears to not work properly for this, I installed Eclipse and now have a different error but I should be able to get past it
On my machine (Windows7, 64bit) I could fix this by setting my execution environment to a 32bit variant of the jdk (I used 1.6.0_23). And I tried a lot of things before...
SHA1's answer did it for me: after updating to the latest sdk/adt, my project refused to build an apk; unchecking the option resolved the issue.
I don't know if the update checked this, or if it was checked before but the new adt screwed things up, but things work again now :)
In my case this worked :
Delete R.Java file in /Gen folder
+
Delete all "R.Android" imports that Eclipse added to some of my java classes !!!
and rebuild the project.
remove -- R.java -- Clean the project and run again.. this worked for me ..
Find the project's folder in your system, enter it's Properties via context menu and deselect "Read only" option. Worked in my case.
This seems to be the source of the problem in many cases, moreover some solutions up there base on copying/rewriting the files in the project what makes them non-read-only.
This is caused by JAVA_HOME not being set correctly. It can be easily resolved by following the steps in this article.
Mine was caused by this problem (incompatibility between ADT and SDK), and was fixed thus:
Eclipse > Help
Install New Software
Add 'https://dl-ssl.google.com/android/eclipse/' to 'Work With'
section and press enter
After developer tools appears on the list, check it and click Next
Restart eclipse once download is finished
I my case, I had to switch from API 21 to API 19, clean and build and everything was fine again. I am using a Mac and apparently API 21 is not fully supported on Yosemite.