StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<blockquote> <p>Now if I ommit from using any class, or whatever it is, at all from that library project inside my main application project, will the output jar/apk file contain the library jar file nevertheless, or won't?</p> </blockquote> <p>If you put the JAR in the libs folder it will.</p> <blockquote> <p>Follow up question to that above (simpler case). Lets say I have library project like above (lets call it MainLibrary), which I DO use in some extend in my main project. Now this library, has other library project/jar referenced (lets say LinkedinLibrary) which it uses internaly. </p> </blockquote> <p>That depends on your project structure. For example: If you just put the JAR of your MainLibrary in the libs folder, the linked projects will be missing. But if you have all projects in your Eclipse workspace and added the projects via properties dialog AND configured it to export the linked libraries too, it will work.</p> <p>That's all what the basic Eclipse build system is delivering. If you're fiddling around with Gradle dependencies it works out of the box - if you get this buggy piece of Android Studio to work. It also works out of the box if you're using Maven, which seems to be way more stable than Gradle in Android Studio at the moment.</p> <p>Generally speaking it depends on your build system.</p> <ul> <li>Maven works out of the box.</li> <li>Gradle too.</li> <li>If you're using ant, you need to write it yourself or use some custom tasks like the <a href="http://ant.apache.org/ivy/" rel="nofollow">Ivy</a> or the Maven dependency plugin.</li> </ul> <p>Edit:/ You also asked if it would be possible. I know no dependency management system which works by source code inspection. So if you don't need an existing dependency you have to remove it yourself.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload