title: Android Studio Java Library Module vs. Android Library Module
body: <p>My desired end result is to have a Project that can output different productflavors of Mobile, Tv, and Wear apps, that share the same code-base. So I would like the codebase to be a dependency for all three app-types, where each app module would only contain activities and interaction with the codebase. </p>
  
  <p>My first idea was to add a "Android Library Module" to my newly created project, but I noticed that this is really just a new app module with its own resources and everything. I would like the codebase to function more like a "Java Library", but it needs access to packages like "android.graphics.Color".</p>
  
  <p>So in short, is the correct way of achieving this result to use a java library that has a reference to an android sdk or am i just going about this the wrong way?</p>
  
  <p><strong>Continuation of this question at</strong>:<a href="https://stackoverflow.com/questions/28157981/does-an-android-library-need-a-manifest-app-name-icon">Does an Android Library need a manifest ,app_name,Icon?</a></p>