Home/ Questions/Q 3457528
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T09:52:16+00:00

I did the following: Create a working Android project (not a library or test

  • 0

I did the following:

  1. Create a working Android project (not a library or test project) in Eclipse. It has a single package called X with an activity X.A.
  2. Create a new Java package Y within the aforementioned project with at least one class Y.C.
  3. Call Y.C from within X.A (that is, call something in the new package from the original package that previously works).
  4. Build and run the Android project.

It builds fine, but throws NoClassDefFoundError on the first line using Y.C, saying it cannot find Y.C. When I Refactor -> Move Y.C into package X (so it is now X.C), the runtime exception is no longer thrown. What’s wrong?

Vague hint: I’ve read that similar problems can happen when the build-time and runtime classpaths get out of sync somehow, but I haven’t found yet how to troubleshoot or fix the issue.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In your AndroidManifest.xml when defining your activities you have to set the fully qualified class name for activities residing in a sub-package or even another package.

    A fully qualified class name would be like com.example.my.cool.app.Activity. Alternatively when only working with sub-packages you can set it like this android:name=".app1.AnotherActivity" when your base-package looks like this com.example.my.cool.

    • 0