Question

I have an Android Eclipse project that I’d like to divide into two sub-projects. The problem is that both projects would need to depend on the generated Android “R” resources (R.string, etc.).

I can’t figure out how I can do this (or if it’s even possible) without causing a circular dependency error. What I tried to do is this:

1. Designate one as the main “Android project,” which has Android nature, contains the generated sources.
2. The secondary project is a plan Java project, but depends on the Android project to resolve the R.string.xxx dependencies.
3. Ideally, the main project would then depend on the secondary project to include needed code, but this causes a cyclic dependency error in Eclipse.

Is there another configuration that makes sense that would avoid the circular dependency?

Answer 1

I’m going to go with the usual “bidirectional dependencies are bad” rule.

I’ll just divide the project into two, where one is the Android project, and the other doesn’t have direct knowledge of the R resources.

Then, whenever I can just pass the R resources as needed from the Android project to the auxiliary project during initialization, or as needed.