Geek Answers Handbook

Android library projects: refactoring and navigation

Currently (this has changed a bit over time). Android library projects become jar files in the link project. There are some problems with this approach: refactoring and code navigation.

Is there a way to reorganize a library that is considering changing dependent projects (e.g. renaming)? Now renaming in the library project will not extend to the dependent project. For each project, I currently have to manually configure them. (Workaround: Remove the library link from the dependent projects and add the library project as a simple link to the Java project.)

Also, moving from a dependent project to a library leads me to decompiled classes inside the project library, but not to the source. Is my Eclipse setup confusing or is it just the current version of the Android library?

+4
source share
1 answer

There is a dirty way to achieve this. You usually add a library to your dependent project, but also like a project in the Java Build Path of the project properties.

In order and export, the library should be above Android dependencies.

+4
source

More articles:


All Articles