How to distribute the android reusable code in a package?

Question

I have developed some reusable android component which is basically a class . This class has some resource dependencies e.g. some png drawables, some xml layouts etc. So this class referenced the auto-generated R file.I would like to distribute this code in a single package like jar file to other developers for use in their applications.

I have read that the only possible solution is to distribute code together with all my resources, which others have to copy to their "res" folder (source).

So I created a jar file having the class file (say MyClass which is in the package com.xyz.android.app) and resources and tried to use this in my new application.

So I added the jar file to my new applications build path using add external jars option in eclipse and copied all the resources to my new application's res folder. (The activity class say MainActivity of my new application is in com.abc.myapplication package, just for the case if it may helpful)

But when I run this new application there is java.lang.ClassCastException in the MyClass class. I tried to debug the application and then I found that in the MyClass class, there is "R cannot be resolved" problem.

Then I changed MainActivity's package to com.xyz.android.app (which is not the way, other developers will be happy to do), But again the same problem.

But When I just copy the source java file such that both MainActivity.java and MyClass.java are in com.xyz.android.app package then application runs fine.

So if I need to distribute such that other users need not to bother these package naming things, how can I accomplish this? Please help !!

Edit

In android.jar, there are also some resources. How are they referenced in a project? How are they used in android classes? There is also android.R file?

Is it not possible to do the same thing i.e. to make jar file like android.jar for my reusable code?

Answer 1

As Nic Strong noted, there is nothing much built into the project to manage this, and current indications are that the upcoming changes to the SDK tools may only help a bit.

I am organizing some other tools to help deal with this problem. I hope to have developer documentation published in a few days.