Question

Here are the steps I have followed so far, with no luck. I am extremely new to Java projects so I suspect I may be missing something obvious.

Using Eclipse, I have created a simple Java project called TestSDK, created within that a package called com.test.testsdk, and within that the following class:

package com.test.testsdk;
public class TestClass {
    public void TestMethod() {
    }
}

This compiles without errors or warnings.

I then export this as a JAR file (TestSDK.jar) using Eclipse and the standard export options (export generated class files and resources, compress the contents of the JAR, generate manifest file). I have tried both sealing and not sealing the JAR which makes no difference.

I then create a new Android application project from File->New->Project in the Wizards list. This compiles and runs without warnings or errors on both the Android emulator and my test device (I get the hello world message).

I then add a reference to my TestSDK.jar file (using a variety of different methods as I will expand on shortly), import it into the main (and only) Android activity, and try to instantiate my TestClass and call TestMethod on it, like so:

package com.apptest.mobilesdktestapp;

import android.app.Activity;
import android.os.Bundle;

import com.test.testsdk.TestClass;

public class MobileSDKTestAppActivity extends Activity {
    /** Called when the activity is first created. */
    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.main);

        TestClass test = new TestClass();
        test.TestMethod();
    }
}

This compiles fine without warnings or errors. When trying to run it on the emulator or the device, however, I get the following error in my LogCat window:

AndroidRuntime    Uncaught handler: thread main exiting due to uncaught exception
AndroidRuntime    java.lang.NoClassDefFoundError: com.test.testsdk.TestClass

Searching the web for the NoClassDefFoundError results in a lot of suggestions on how to import the JAR file such that the class path is correct. As a result, I have tried all of the following methods of importing the JAR file:

1. “Add External JARs…” from the Libraries tab of Java Build Path in the project properties, followed by checking (or not checking, I tried both) the JAR in the Order and Export tab. Also tried moving the JAR to the top of the Order and Export list, which made no difference.

2. Creating a “libs” folder in the project, and adding the JAR there. I confirmed that the JAR is then also added to the “Android Dependencies” thing in the project list. Also tried right-clicking the JAR file and selecting Build Path->Add to Build Path which made no difference.

3. Moving the JAR into my Android Application project directory and doing “Add JARs…” instead of external JARs as in step 1, also all permutations of exporting or not and moving it to the top of the order list or not.

I have subsequently downloaded other 3rd party SDKs that are packaged as JAR files and included those in the very same Android application project, and those have all worked fine using any of the 3 methods above (I am able to instantiate classes from those SDKs and use them without error), which leads me to believe I am missing something or doing something wrong in my TestSDK project and/or class which is preventing it from being used in the Android Application project.

As I said, I am very new to Java, so I’m hoping it’s something simple that I’ve overlooked. Any help or guidance would be appreciated.

Answer 1

I think I figured out what the issue was (or at least how to fix the issue, I’m still not 100% sure what I did)–

When I created the original TestSDK java project, I let it target the default JRE in the project creation dialog (jre7).

Checking the project properties of a new Android Application project, the Java Compiler section has “Compiler compliance level” set to 1.5. So, I tried recreating my TestSDK project again, but told it to use J2SE-1.5 as the execution environment instead of the defalut jre7.

After doing this, exporting the JAR and importing it to the Android project’s libs directory, I am now able to instantiate the TestSDK classes and use them just fine without the NoClassDefFoundError exception.

Best guess is that the Android application was being compiled against an older version of the JRE than my TestSDK class (which I believe was targeting JavaSE-1.7), causing the issues. Matching the two versions up has solved it.