After days and days of hard work, I have my android project without errors in Eclipse.
I used build.gradle. Now, I can add library in that file writing "compile 'com.somelib.version'.
Now, I can type 'gradle clean' and 'gradle build'. These commands don't show errors. So, I think project added dependencies correctly. But I add Gson, or different library with gradle, how can I use it?
Eclipse give eror if I type 'import com.google.gson' (in this example). So, maybe I forgot a step before having dependencies working?
You may want to run these gradle commands:
cleanEclipseClasspath
eclipseClasspath
This worked for me when I had your issue.
I use the latest Android Annotations 2.6 and IntelliJ IDEA.
Sometimes I always keep having problem with the annotations / classpath / compilation order. Seems to occur irregularly. I had the project compile earlier today, then changed a res/layout-xml file later on, then I try to build the project and get an error.
But there are no syntax errors or anything in the xml nor java source files.
Problem is that the annotated class doesn't find it's original class, getting
cannot find symbol class Intro
error.
My project structure:
/src/
/app/activity/Intro
...
/gen-annotation-processed/
/app/activity/Intro_
...
/gen
...
My IDEA annotation preferences:
Processor path:
/path/to/project/ext-libs/androidannotations-2.6.jar
Processor FQ Name:
com.googlecode.androidannotations.AndroidAnnotationProcessor
Source folders in the project's Android IDEA module:
gen
gen-annotation-processed
src
Error login in IDEA when building the project (via IDEA, no ant or maven):
(Class "Intro" exists in the src folder and has no errors in it.)
Update: I have it working now, although not sure what/where I changed something after playing around with settings back and forth. It might actually just be an issue with IDEA and not actually android-annotations related, not sure yet.
What usually seems to work is: do a Rebuild (might throw compile errors, ignore). Then do a Build (not a complete rebuild). For some reasons, the multiple compilation runs don't work properly when doing a rebuild, need to do the rebuild+build combination.
Above mentioned problem was an issue with the new build system that was introduced with IDEA 12, in combination with an issue of AA 2.x, which is meanwhile fixed in AA 3.
See:
http://github.com/excilys/androidannotations/issues/423
http://github.com/excilys/androidannotations/issues/471
(Anyhow, as #outlying mentioned, maven is a good idea in general to make it independent of the IDE at all.)
Have you tried this link http://www.ashokgelal.com/2012/12/setting-up-intellij-idea-12-with-maven-actionbarsherlock-roboelectric-androidannotations/ ?
It works like a charm for me, I was able to setup few projects with AA on IDEA
You have to enable android annotation processing on File->Other Settings->Default Settings..
goto of your app build.gradle
and remove
apt "org.androidannotations:androidannotations:{xxx}"
compile 'org.androidannotations:androidannotations-api:{xxx}'
then put it again
apt "org.androidannotations:androidannotations:{xxx}"
compile 'org.androidannotations:androidannotations-api:{xxx}'
and rebuild
it worked for me
I have used the isEmpty and isBlank methods of apache's StringUtils Class. These methods worked in a fine manner, after couple of weeks suddenly i got the error
java.lang.NoClassDefFoundError: org.apache.commons.lang3.StringUtils
I was confused why this error happened suddenly.It would be fine if anyone help me to understand this suddenly happened.
People Saying that apache might have changed the definitionin their JAR file, is it a right one,i really confused why this suddenly happened , i removed the old jar from my build path and downloaded the same version of New Jar and added it to Build path, then this issue is resloved.
It is happening in the Market Code , there's no interaction with ADT and market code
so really confused on this issue?
This occurred to me too - after updating the Android SDK Tools. In current version (19), what you need to do is:
make libs/ folder in project's root directory, and put all jars there (folder's name is fixed "libs")
after this, go to project properties --> Java Build Path --> Libraries, and remove all custom jars you previously added
NoClassDefFoundError says NoClassDefFoundError is Thrown if the JVM or a ClassLoader instance tries to load in the definition of a class and no definition of the class could be found.
Maybe startup script is overriding Classpath environment variable.
although there are many questions with a similar title, I could not find the solution to this issue.
I have an Android project in Eclipse which references ActionBarSherlock 4.0.2 as Android library. In addition, I have added the JARs for ACRA and Google Analytics in the /libs folder. The support v4 jar is taken from ABS libs.
The project's Java Build Path looks like this
When exporting through the wizard I get the "Conversion to Dalvik format failed with error 1" error.
Cleaning, removing all Android Dependencies and clicking on Fix Project Properties and cleaning does all not work.
Any idea?
EDIT:
I missed some info: I'm doing this on Mac OS 10.6.8, Eclipse Indigo, Android SDK Tools r19 and ADT plugin v18.
project.properties file includes the proguard.cfg file: commenting it does avoid the issue.
I actually managed to overcome the issue, here soem details if they can be of use to anybody:
I first tried everything from clean to close/reopen project etc etc etc
I finally too the latest beta of proguard from http://sourceforge.net/projects/proguard/files/ and replaced the /lib folder in android-sdk-macosx/tools/proguard with the one from the beta version (proguard4.8beta1) and .. it works!
I had the same issue after updating to ADT 20 (released with Jelly Bean), and similarly, all the old solutions (clean, rebuild, etc.) didn't help. Taking a clue from omoling's answer, I updated my Flurry jar to the latest from their website... and the problem cleared up.
So, if you're having this problem, try updating any/all external libraries that your project uses.
Encounter this problem when trying to Build Project getting such output in console:
[2010-07-19 23:29:23 - myProject]
trouble processing "javax/net/SocketFactory.class":
[2010-07-19 23:29:23 - myProject]
Attempt to include a core VM class in something other than a core library.
It is likely that you have attempted to include the core library from a desktop
virtual machine into an application, which will most assuredly not work. If
you really intend to build a core library -- which is only appropriate as
part of creating a full virtual machine binary, as opposed to compiling an
application -- then use the "--core-library" option to suppress this error
message. If you go ahead and use "--core-library" but are in fact building
an application, then please be aware that your build will still fail at some
point; you will simply be denied the pleasure of reading this helpful error
message.
[2010-07-19 23:29:23 - myProject] 1 error; aborting
[2010-07-19 23:29:23 - myProject] Conversion to Dalvik format failed with error 1
I was looking for my project to use the package javax, not found, clean all also does not help. what I am doing wrong?
Update
Sorry guys, but I could not find good fix for that, I want to emphasize the fact, that i dont use SocketFactory class in my project at all! source code was not changed before this problem, and that's why i think that problem in eclipse or adt or something else, BUT if i use ant(generated by sdk) to build this project there is no problem!!!
I solve this problem by removing Eclipse, Android SDK, Eclipse workspace, and just reinstall them, after this all works fine for now.
Hope this will help someone.
I had the same problem..
This worked for me
project-->properties->java build path->libraries-> remove all including android jars
now go the project browser, right click on the project you are working on,
then android tools---> fix project properties...
do a clean and then build...
I solved the problem (at least for me).
Here's what I did:
Go to Project » Properties » Java Build Path » Libraries
Remove all except the "Android X.Y" click OK.
Go to Project » Clean » Clean projects selected below » select your project and click OK.
That did the trick for me.
Hope it works for you as well
Update: well actually I might have to retract my opinion.. the actions removed the error messages but now I am missing certain classes and methods... arggghhhh
I just restarted Eclipse, and the error didn't appear anymore!
I had the same problem,and solved it as follows:
First clean all jars; (This problem must because your some jars)
Delete the project;
Reimport project;
Make sure your sdk is right, and project select one sdk version;
(This is my issue to solve the problem) Right click your project, and select "build-path", next select "add Librarys", and add your private jars;
clean-build, the problem has fixed;
I just had the same problem and I tried all of the solutions listed here with no success (I was starting to get annoyed). Then I removed the project from the workspace and then imported it again, and there were no problems!
This happened to me this way,
I have a quite an old project which I had to start working again today. I use 'Universal Image Downloader' library for basically every project where I have to deal with lots of images. So in this old project I had the source files of 'Universal Image Downloader' included to it's 'src' path. Back then I was a newbie and slowly I started developing my own library which could handle every day simple Android development tasks very easily. Obviously I included the 'Universal Image Downloader' to this.
After dusting off the old project today the first thing I did was to reference my library to speed up the development process but as I was trying to debug I ran into the "Conversion to Dalvik format failed with error 1" over and over again. First I thought it was the support library but even after clearing all libraries and adding only mine and doing a quick 'Fix project properties' I still got it. After trying various solutions I noticed this in the console "java.lang.IllegalArgumentException: already added: Lcom/nostra13/universalimageloader/cache/disc/BaseDiscCache;"
It was as simple as that... I'm trying to compile a class which has already been compiled.
Solution : I just simply removed all the class files I got from 'Universal Image Downloader' library from the 'src' directory. Since my library references "Universal Image Downloader" library the old project started working just fine.
Hit same problem shown on your log when trying to run an example project which was imported into eclipse.
Additional Info: in eclipse's Problems View I see the following error:
"The project cannot be built until build path errors are resolved"
In my case the imported project find the libraries just right(by just right I mean I can see the external path to each of the android libs in this case 2 libs, android.jar and maps.jar). So no shuffling of libs in my case, but might be your problem.
I followed Spock's suggestion of cleaning the project which I had to clean multiple times until it somehow resolve its issues. After, issue was solved I had to specify an AVD for the project to run and soon after was up and running on the emulator. Also, note that my eclipse is set up to Build Automatically.
In my case I'm not missing any class files or anything after the clean as the build is properly generating them.
Regards!
I was getting the same error. My problem was that i had an android device hooked up to debug with. As soon as I unplugged it I was able to export.
The answer I found was checking the source and library build path in the project's properties. Most likely there will be a duplicate as in something being referenced in both the source and library tabs. So delete the extra in the source tab and then clean the project and you should be good to go.
Either:
javax.net.SocketLibrary is in your source code, or
javax.net.SocketLibrary is included in a JAR file in your project
Under certain conditions it gets its knickers in a twist and the best fix I've found is to remove referenced jars, clean, add them back in and then compile again.
I believe the error can be caused by including the same classes twice.
This error will also occur (and you won't be able to get rid of it by cleaning) when using classes that are not part of the Android environment.
To summarise the information in the link bimbim.in provided (well my understanding when I glanced over it)
The Android Davik VM tries to compile the jars but finds some stuff that it can't compile to .dex files
so
Just create a "lib" directory in the root of the project (where the src, bin res directories are) and add them to the build path. Project Properties... Java Build Path... Libraries.. Add JARs..
I could resolve this issue by creating a new project, looks like the some project settings were creating this issue and could not really find the root cause for that. But, dumping the existing source code onto the new project resovled this issue. If anyone has found the root cause for this problem pls do let me know.
I had the same problem and solved it as follows:
- Go to Project/Properties/Java Build Path/Libraries and remove all JARs except Android
- Do a project clean
- Add the JARs again as External JARs (first time I added them internally, so that might be the problem)
After that the error was gone.
I solved the problem by updating available packages in the Android SDK et AVD manager. No need to remove Eclipse.
Whenever the Project is having the ambitious data. This problem is caused. May be android can't able to find which one choose.
From what I understand, this same cryptic error could be caused from a wide variety of reasons. I've got "Conversion to Dalvik format failed with error 1" error too. In my case the problem was that for some reason Project -> Properties -> Java Compiler was not set to "Enable project specific settings" with proper Java 1.5 settings, but was left to defaults instead (1.6 in my case). Debug, build and test on devices/emulators worked fine, but export always failed with the above error message.
If unsure about the proper settings, create the same project on some alternative location and just copy all needed files from the old project into the new one. This fixed the issue for me.
The next problem with the same error message came from using proguard. Updating to the latest version by replacing the one that came with android sdk, fixed that.
Hope this helps
My problem was having a jar file in my src folder. Removing jars from the build path works, but only if you don't need the jar in question. For people who need the jar in question, make sure that your jar file is not in the project folder (maybe just src subtree, but I would keep it separate to test). Put it on your desktop or something and try the "Add external jar.." option. Be sure to remove the jar from the project filesystem before adding another external. Having both is what causes the problem.
I have done it as the instruction of the first answer and it works.(Linux)
I think the problem may caused by SDK or ADT updates.
I do have to clear all the lib in Java Building path and then use android tools to fix the project. After cleaning and rebuild, it works as before.