更新我的ADT插件后。当曾经创建的任何项目appcompat V7文件夹中创建。我用这种依赖性。但问题是假设我有5个项目即可。它使5种不同的文件夹，该怎么办？
解决方案这是ADT / SDK更新的一部分，它不是一个坏的事情发生。它可以确保您的应用程序具有完全支持这是在API 14+实现的ActionBarActivity的。它会得到默认创建每一次，但有一点工作，你可以让你的文件了。我只是有一个单一的appcompat_v7，每当我创建一个项目，我们称之为SampleApplication，创建appcompat_v7_2。
如何重新引用您的库 -右键点击SampleApplication
进入属性
点击Android的
滚动至底部的库部分。
点击.. appcompat_v7
点击删除
点击添加
点击appcompat_v7
点击应用`
现在你已经提到的preexisting库。现在，您需要删除旧的额外复制appcompat_v7_2库。我这样做如下：
在删除重复的副本 -就在你的工作空间的Package Explorer中点击appcompat_v7_2
点击删除
如果（删除选项包含复选框物理工作空间中删除）{
选中该复选框以从硬盘驱动器和preSS确定删除物理文件夹;
}
其他{
去你的物理工作空间（在Windows中，类似于C：...... 工作区）;
查找appcompat_v7_2;
右键点击你的物理工作空间appcompat_v7_2;
点击删除;
}
重启Eclipse;
引用您的pre-现有的库后，你可能会得到您的应用程序，在控制台读取，发现错误Android的支持 - v4.jar在依赖列表2版本...... 为了解决这个问题，进入你的工作空间中的应用库文件夹，删除 Android的支持-v4.jar 。
这是不理想的，因为它需要为每个应用程序位安装的。但是，它的工作原理。您也可以取消选中创建活动，当你创建你的应用程序的项目，也不会添加库（而且，很明显，将不包括您的主要活动）。
作为另注，显然对一些人来说它不包括图书馆，如果你的最低SDK版本的应用程序是11+。但对我来说，它总是包含它，所以这是我周围的方式。
重要FIND - 请阅读
所以，我决定开始一个库项目我工作的一个新的工作区和碰到一些有趣的事情。我输入我的appcompat_v7到我新的工作区从我的旧的工作区，并确保点击复制项目进入工作区。现在，它不会每次我添加了一个新的项目到我新的工作区时添加appcompat_v7。促使我实现一个可能的修复：
尝试移动appcompat_v7从工作区文件夹到另一个文件夹，并且导入它回到您的工作空间并确保单击复制项目到工作区的。
不知道这只是一个小故障或东西，但它的工作两次，当我重新测试了！
After Updating my adt plugin. When ever I create any project "appcompat v7" folder is created . I used this dependency. But problem is suppose I have 5 projects then. it makes 5 different folders what to do?
解决方案This is part of the ADT/SDK update and it is not a bad thing to happen. It ensures that your app has full support of the ActionBarActivity that was implemented in API 14+. It will get created each time by default, but with a little work you can keep your files down. I simply have a single appcompat_v7, whenever I create a project, let's call it SampleApplication, appcompat_v7_2 is created.
How to re-reference your library -Right click on "SampleApplication"
Go to "Properties"
Click "Android"
Scroll to the bottom's "Library" section
Click "..appcompat_v7"
Click "Remove"
Click "Add"
Click on "appcompat_v7"
Click "Apply"`
Now you have referenced your preexisting library. You now need to delete your old "extra" duplicate appcompat_v7_2 library. I do this as follows:
Deleting duplicated copy -Right click on "appcompat_v7_2" in the Package Explorer of your workspace
Click "Delete"
if(Delete Options contains checkbox to delete from physical workspace){
Check the checkbox to delete the physical folder from your hard drive and press OK;
}
else{
Go to your physical workspace (In Windows, something like C:......workspace);
Find "appcompat_v7_2";
Right click on "appcompat_v7_2" in your physical workspace;
Click "Delete";
}
Restart Eclipse;
After referencing to your pre-existing library, you may get an error with your application that reads in the console as Found 2 versions of android-support-v4.jar in the dependency list,... To solve that problem, go into your applications libs folder in your workspace and delete the android-support-v4.jar.
It is not ideal as it requires a bit of setup for each application. But it works. You can also uncheck "Create Activity" when you are creating your application project and it won't add the library (but also, obviously, won't include your main activity).
As another note, apparently for some people it doesn't include the library if your minimum sdk version for your application is 11+. For me, however, it always includes it, so this is my way around it.
IMPORTANT FIND - PLEASE READ
So I decided to start a new workspace for a library project I am working on and came across something interesting. I imported my appcompat_v7 into my new workspace from my old workspace, making sure to click on Copy projects into workspace. Now it doesn't add appcompat_v7 every time that I add a new project into my new workspace. Led me to realizing a possible fix:
try moving appcompat_v7 from your workspace folder to another folder, and the importing it back into your workspace making sure to click Copy projects into workspace.
Not sure if it was just a glitch or something, but it worked twice when I retested it!
相关推荐
最新文章