I am facing a so weird issue with my eclipse. Android projects are not running in my eclipse
I'm using
Eclipse version 4.4 Luna ,
android SDK latest API level 23
(even earlier versions is not working ).It was running well till some days ago , and all other java projects running fine like web and desktop etc..
Whenever I am running the android project it shows the error dialog box, though no errors are there in the project(for a new project also), I have tried clean build, cleared cache, updated eclipse adt , and is there anything left I need to try other than formatting PC?
Well ,after some struggle I have found out what is the actual problem. It was my debug.keystore file.
I have got an error in my console saying Debug certificate expired
Well I have found my debug.keysotre file in here %USERPROFILE%/.android and deleted it. Eclipse itself will generate a new one when compiling a new project. You may need to clean and then build to generate the certificate.
Thanks everyone for your support.
Problem solved !!! :)
Related
The plugin Workspace(java) that I use while working with eclipse is quite big approx 250MB. Everytime I open a fresh eclipse session with the Workspace, it gives me errors. However reloading the target platform plugins just solves the problem.
When most of the projects are closed & eclipse restarted the error that is described above & the projects which show errors previously are not there & the code runs fine.
I am keen to know, what does a reload do different & want to make it possible to open the workspace without any errors.
Using eclipse oxygen solved the issue. The workspace is loaded directly without any error as was with eclipse mars.
When I installed Android Studio on my mac (OSX Mavericks) and created a project, I got this error:
Failed to sync Gradle project 'project name'
unable to find method 'org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V'
When I first had this problem I had gradle-1.12 installed. I then installed gradle-2.1 and still the same problem. I then installed gradle 1.1 and still the same problem.
I've been trying to fix this problem for the past week to no avail.
Look in ~/Library/Java/Extensions. I had an alias in there for slf4j-api.jar, amongst other old things. Removed that (actually I deleted the whole ~/Library/Java directory :-) and it works fine now.
i have a little vaadin project for a school project that originally deployed well and worked.
i am using jboss as 7.1.1, vaadin7 and jdk8. My target platform is a raspberry pi running raspbian os.
so i am using the pi4j library to access the gpio interface of the raspberry and everything worked just fine until i implemented a check for null when creating a new instance of the web page. at first the error was because somehow the "jboss/standalone/deployments/roboterarm.war/WEB-INF/..../classes" directory became empty. afterwards the error came to eclipse as i could not use the pi4j library anymore. i did not touch the libraries and i can't figure out why it suddenly stopped working. i reinstalled eclipse, jboss and redownloaded all the libraries but i still can not use anything, not even in normal java applications!
afterwards i grabbed a copy from SVN that used to work normally but no luck there either, i can not use the pi4j jar-files.
everything looks fine to me there, yet it fails to give me code completion or compilation
i also tried creating a new vaadin project and c&p'ing the source code into the new project but the jar files are not recognized there either.
What am i doing wrong? how can i fix this? thanks in advance!
Eclipse buildpath, clearly indicates that your JRE is not properly added. Add your JRE to your build path, using the option Add Library.
I implemented the current version of ActionBarSherlock to my Android Project.
Everything works fine and I don't get any errors.
But when I try to debug or export my project I don't get an .apk-file out of my project. Just a .jar-file with the name of my project.
I've read about some problems the SDK had with building projects that contain external libraries but this was at SDK version 14 and so I hope, this bug is fixed...
So there might be another cause for this problem.
Does anybody know a possible solution?
You cannot get *.jar file as the result of building Android project. This seems very strange to me. There must be something wrong with your project settings (if you changed them), or the project you build is of the wrong type (i.e. it is Java Application instead of Android Application).
You didn't mention which IDE do you use, but I assume you use Eclipse.
Make sure you have installed Android SDK and Eclipse ADT correctly (just in case).
Next thing to try is to create a new Android Application project from existing sources (there should be such option during the process of creation).
wow.. some of my dreams just got true :) Great Tools! Still I've got a problem with it. I've got a pretty fresh install of eclipse 4.2 + Android Development Tools 20 + Google App Engine Tools for Android 3.0.1 + Google Plugin for Eclipse 4.2 3.0.1
When I create a new clean Android Project and try to "generate app engine backend" I get an error and a lot of missing dependencies and code.. Error message is useless and console tells me everything worked
Error: Error in Generating Backend Project
Console: DataNucleus Enhancer (version 1.1.4) : Enhancement of classes
DataNucleus Enhancer completed with success for 1 classes. Timings : input=80 ms, enhance=44 ms, total=124 ms. Consult the log for full details
In my Create Wizard I also don't have the option for App Engine Connected Android Project
I double checked I've got all dependencies freshly installed via "Install new Software"
Link to Installed Software: http://sharetext.org/EFS2
I had the same Problem with Eclipse 3 and deleted it and made this new fresh install of Eclipse 4.2
I'm having the exact same problem. Have you made any headway?
EDIT
Based on this: https://groups.google.com/forum/#!msg/google-plugin-eclipse/QIgMgvAdn3o/hdiLLD3HQeQJ I think we're supposed to hold off until the documentation is updated.
I had too the same exact problem. Instead of Eclipse 4.2 try using Eclipse 3.7 Indigo. It did work for me.
It was a bug which got fixed in one of the later versions, if you run into this check to update your GooglePlugin for Eclipse