3rd party jar

by Michael Lippautz » Tue, 10 Feb 2009 06:40:01 GMT


Sponsored Links
 Hi,

Having a problem here with including a 3rd party jar and couldn't find
any proper solutions on the group so far.

Compiling the HelloWorld app. with an additional 3rd party jar
(cglib-nodep). The jar is in the lib/ folder and has been added to build
path (add jar).

Compiling gives these warnings (about ~30 times):
warning: Ignoring InnerClasses attribute for an anonymous inner class
that doesn't come with an associated EnclosingMethod attribute. (This
class was probably produced by a broken compiler.)

I then tried to create the dex file myself (dx --dex --output=xx.dex
xx.jar) and succeeded without any errors. As far as I know an
incompatible jar file (incompatible byte code) shouldn't have passed
this one. Am I right here?

The problem is that by adding another 3 external jars the number of
warnings increases, compiling fills the buffer completely and finally
crashes the workspace.

Did I miss something?

I tried another approach by adding them as user lib but got an undefined
reference at runtime. (The .dex and .apk were far too small, so I think
they didn't get included)

Libs were:
cglib-nodep
commons-logging
antlr-runtime



--~--~---------~--~----~------------~-------~--~----~



3rd party jar

by Michael Lippautz » Tue, 10 Feb 2009 06:40:33 GMT


 Hi, (if you already received the message, sorry for that!)

Having a problem here with including a 3rd party jar and couldn't find
any proper solutions on the group so far.

Compiling the HelloWorld app. with an additional 3rd party jar
(cglib-nodep). The jar is in the lib/ folder and has been added to
build
path (add jar).

Compiling gives these warnings (about ~30 times):
warning: Ignoring InnerClasses attribute for an anonymous inner class
that doesn't come with an associated EnclosingMethod attribute. (This
class was probably produced by a broken compiler.)

I then tried to create the dex file myself (dx --dex --output=xx.dex
xx.jar) and succeeded without any errors. As far as I know an
incompatible jar file (incompatible byte code) shouldn't have passed
this one. Am I right here?

The problem is that by adding another 3 external jars the number of
warnings increases, compiling fills the buffer completely and finally
crashes the workspace.

Did I miss something?

I tried another approach by adding them as user lib but got an
undefined
reference at runtime. (The .dex and .apk were far too small, so I
think
they didn't get included)

Libs were:
cglib-nodep
commons-logging
antlr-runtime

--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Other Threads

1. Problem to open SMS after deleting another with my widget...

Hi,

I guess the SMS api is not open for public use yet. There are no
comprehensive docs on this topic as well. The way you are accessing
the Content Provider might change in the future and hence, your app
will break.

The SMS table is tightly coupled with the notifications as well. You
need to manage them, but at this point, it seems impossible to do so.

http://tech-droid.blogspot.com/2009/09/sms-blocking-in-android.html

Thanks and Regards,
Kumar Bibek




-- 

2. OE 1.2.1 usb internet tethering does not work



you mean i cannot use internet tethering on OE 1.2.2? good luck, i did
not upgrade :)


-- 
Best Regards,
David Shen

http://twitter.com/davidshen84/

-- 

3. How to pass a property value argument to an instrumentation test runner

4. Cannot get PhoneNumber on Real device but code works in Emulator

5. General question: Can't we have 2 projects(same) in 2 different locations and import them in eclipse?

6. HTML parsing with JAVA

7. Customizing in Coming /Out going call screen