| How to force re-build of external jar on run of android app? [message #760940] |
Mon, 05 December 2011 11:35  |
Eclipse User |
|
|
|
This might be a fairly general Eclipse question but since I've run into some Android-related specifics in my development before, I am asking my question here. I am fairly new to both Android dev and Eclipse so I suspect this q might be fairly basic.
I have an Android project (let's call it pA) that depends on an external JAR exported in a regular Java project (let's call it pE). Right now, when I change something in pE's source and then want to run the pA app, I follow these steps:
1. Modify source in pE
2. Delete its existing JAR
3. Export pE
4. Do a refresh of pA
5. Run/debug pA
I am probably doing extra work here. What's the easiest way to force a re-build/re-export of pE when I run/debug pA? Can I do steps #2-4 automatically by performing a single operation within pA?
Thanks!
|
|
|
|
| Re: How to force re-build of external jar on run of android app? [message #761497 is a reply to message #761440] |
Tue, 06 December 2011 09:52  |
| Eclipse User |
|
|
|
Satyam Kandula wrote on Tue, 06 December 2011 08:31I don't know if it will be different with Android development, but with normal java projects, one generally adds the pE project as a dependency of pA and that should work.
I tried that by going to Properties of pA -> Project references and checking pE. However, when I tried to run pA, I got this:
java.lang.IllegalArgumentException: already added...
...
Conversion to Dalvik format failed with error 1
Any idea why?
Thx
|
|
|
Powered by
FUDForum. Page generated in 0.05990 seconds
Home