library-project

I have a main Android application that is using an Android library project. When I change my library project and Build Project or Build All the changes are not detected in main project until I clean the main project or close and reopen Eclipse. How con I solve this problem? Is there any rapid solution? Update I am using: Eclipse 3.7.1 Android SDK API 15 Rev 3 Android SDK Tools Rev 19 Android SDK Platform-tools Rev 11 Bobs Solution 1) I clicked on Android Dependencies in Package Explorer and pressed F5 (refresh) and built the main project and problem solved. Solution 2) this answer also works

One of the newer functions of Android is the ability to create a Library Project . This is great for unit testing and sharing common functionality across many apps you may be developing, but I seem to have stumbled upon a bug in their implementation. When you have the following situation: - LibraryProject contains LibraryProject/libs/folder/lib.jar in it's build path. - ReferencingProject references LibraryProject . From ReferencingProject you don't have access to anything inside lib.jar (Such as constant's used to communicate with methods in the Library Project ). A solution to this is to

I'm creating a component for the Xamarin Component Store, providing a Library for Android and iOS. I've put NUnit tests into both library projects but I can't run the unit tests. Is it possible to execute tests in a Android/iOS library project? Ben Bishop If you make your library a PCL, you can create a NUnit project that links to the PCL and run your tests that way: https://dzwonsemrish7.cloudfront.net/items/0H3W383D2e031q1p3s40/Screen%20Shot%202013-08-12%20at%207.56.05%20PM.png?v=d5aac873 Xamarin also provides a NUnitLite test runner for iOS: http://docs.xamarin.com/guides/ios/deployment,

Project A is an android library project in my workspace(via project properties->android->library: is library). Project A declares classA. Project B uses project A (via project properties->android->library: add...). Project B instantiates classA. When I use F3 ("open declaration") over the classA instance in project B, it leads me to the classA.class in the A.jar that is included in B, built from A. Is there a way to go directly to the source classA.java in project A rather than looking for it in the package explorer? I think this is new to ADT14, formerly there were X_src folder for each

I found a few threads reporting a similar problem but none of them really offers something that I haven't tried already. An innocent such call: mActivity.startActivity(new Intent(mActivity, MyEditPreferences.class)); with the following in AndroidManifest.xml: <application> <activity android:name="MyActivityLib" /> <activity android:name="com.example.baseapp.MyEditPreferences" android:label="@string/app_name"> </activity> </application> Triggers the following exception: 06-14 14:06:50.297: ERROR/AndroidRuntime(9272): android.content.ActivityNotFoundException: Unable to find explicit activity

I have a project that references two library projects. After upgrading the ADT and SDK tools to version 17 , the app crashes as soon as it hits a reference to a class defined in one of the Library projects. Errors such as: Unable to resolve superclass of Lcom/my/package/name/MyActivity; (118) Link of class 'Lcom/my/package/name/MyActivity;' failed VFY: unable to find class referenced in signature (Lcom/my/package/name/MyActivity;) and: FATAL EXCEPTION: main java.lang.VerifyError: my/package/name/util/SomeClass at my.package.name.App.onCreate(App.java:120) at android.app.Instrumentation