|Re: Setting up default project setup preferences [message #1271983 is a reply to message #1271936]
||Sun, 16 March 2014 20:00
| Russell Bateman
Registered: July 2009
Location: Provo, Utah, USA
On 03/16/2014 11:44 AM, Zach Caudle wrote:|
> So a lot of Android developers have been running into the "problem"
> where the appcompat_v7 library is getting created in the eclipse
> workspace with every application, even if the application doesn't need
> it (is API 11+). Apparently, this is because the the recent sdk update
> has told the eclipse plugin that this is a good idea. I have seen a few
> articles talk about how it is a good idea to keep the library, but that
> you can edit what libraries are included by default on a project build.
> This is really intriguing to me as I often create multiple projects in
> sequence that utilize the same/similar libraries. However, I can't seem
> to find any information on how to actually do this. Does anyone know how
> to set what eclipse does by default on the creating of a project,
> specifically when it comes to dependencies?
An Eclipse Java project and Dynamic Web Project organize their
particulars along these lines in the .classpath file in the project.
This file is almost empty immediately after the new-project wizard runs.
It's been a while since I wrote Android software. I don't remember the
exact details, which may have changed anyway, of how a new Android
project is set up, but I'm pretty certain it's the ADT plug-in that
controls or implements the new-project wizard. For this reason, you'll
likely get more help with this question in an Android forum.
Powered by FUDForum
. Page generated in 0.02843 seconds