使用 svn:external 将 Android 库添加到项目中
是否可以？
这里有三个使用通用 Android 库的游戏 - http://server.us/svn/greatlib。
我的梦想（我的 PM 也是如此；）“一键结帐”。
在我必须
- 签出游戏之前（ http://server.us/svn/game1 ）
- 签出 lib
- set lib在属性中。
我正在努力改进它。
我的方式：
我用 SVN:external 做了一些操作。
- 将库目录添加到游戏项目（libraries/greatlib）中，
- 设置 svn:external 像这样“/svn/greatlib/libraries/greatlib”
- 将“android.library.reference.1=libraries/greatlib”添加到default.prop中。
- 失败：无法添加 Android 库，它不是工作区中的项目
您有想过吗？
Is it possible?
There are three games which use common android lib and situated here - http://server.us/svn/greatlib.
My dream (and my PM's too ;) to "checkout by one click".
Before I have to
- checkout game ( http://server.us/svn/game1 )
- checkout lib
- set lib in properties.
I'm trying improve it.
My way:
I have done some manipulations with SVN:external.
- added library dir into game project (libraries/greatlib)
- set svn:external like this "/svn/greatlib/ libraries/greatlib"
- add "android.library.reference.1=libraries/greatlib" into default.prop.
- Fail : cannot add android library which is not a project in workspace
Have you any thought about this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
回顾这篇伟大的旧文章：
http://msmvps.com/blogs/jon_skeet/archive/2009/11/02/omg-ponies-aka- humanity-epic-fail.aspx
这是我看到 ADT 时的设想14 预览：
希望图书馆项目正在建设中通过 Eclipse 中的库项目类路径容器作为 jar 引用包含在内，关闭引用的库不会影响类路径容器中所述 jar 的存在。
不幸的是，
我不明白 svn 欺骗将如何让你克服 ADT 插件本身的基本问题：您无法使用基于 Eclipse 的构建工具链引用未打开且位于工作区中的库项目。对于 Ant 构建来说可能是一个完全不同的故事。
话虽如此，谷歌做出了一项崇高的尝试，将图书馆项目推广给一流公民。还有一些工作要做。
Hearkening back to this great old post:
http://msmvps.com/blogs/jon_skeet/archive/2009/11/02/omg-ponies-aka-humanity-epic-fail.aspx
Here is what I envisioned when I saw the ADT 14 preview:
The hope was that since the library projects are being included as jar references via the Library Projects classpath container in Eclipse, that closing the referenced library would not impact the presence of said jar in the classpath container.
Unfortunately,
I don't see how svn trickery will get you past the fundamental issue that is with the ADT plugin itself: you cannot reference library projects that are not open and in the workspace with the Eclipse-based build toolchain. Might be a totally different story with an Ant build.
That being said, Google made a noble attempt to boost library projects to first class citizens. Still some work to be done.