It seems that there are solutions to the issue of having jars with resources. It probably needs to be incuded as part of the core Android development Eclipse extensions rather than individual developers hacking out sorta-solutions. The Google engineers are surely aware of this limitation because it impacts them as well. Models are available in other java development environs so maybe they will serve as inspiration.
On Wed, Dec 16, 2009 at 10:11 AM, gudujarlson <[email protected]> wrote: > It is quite a bummer that Android resources cannot be distributed in a > jar. One possible work-around that comes to mind is writing up a > simple tool to convert resources to java literals and compiling these > into your project. For example: > > public static final byte myresource[] = {0x45,0x23,0x8F}; > > Obviously, real resources would be much larger. > > As long as you never need to call an API that expects a Android > resource ID, this should be a poor mans replacement for Android > resources. I am going to try this approach with a reusable library > that I am working on. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
