在究竟是什么项目会受到欢迎更多细节。我的理解是，你想不泄露源出售库（一套组件/工具，开发人员可以在他们的应用程序集成）。

More details on what exactly does your project would be welcome. My understanding is that you want to sell a library (a set of components/tools developers can integrate in their app) without disclosing the source.

正如你所说，你可以不包括Jar文件的资产/资源。

As you stated, you can't include assets/resources in Jar files.

这是Android的图书​​馆计划将迫使你让源$ C ​​$ C是看得见。正确的许可条款能帮助你把周围的源$ C ​​$ C使用的法律围栏，但......嗯，你知道是什么人做的牌照......也许有些code混淆（而不是在公众可​​见的方法）可能会有帮助。

An Android Library Project would force you to let the source code be "visible". Proper licensing terms could help you put legal fences around source code usage but... well, you know what people do with licenses... Maybe some code obfuscation (not on the public visible methods) could help.

我不知道包括以＆lt如何共享库;使用库＆GT;看到的工作，但这些例子依赖于系统（地图API仅适用于官方谷歌接受设备，Sprint公司的Evo前置摄像头......），可能需要将系统内建成。也许一些超级用户权限，将有助于增加一个，但这必须在每台设备上完成的，其中使用库的应用程序将要运行...

I'm not sure about how "shared libraries" included with <uses-library> work, but the examples have seen are system dependent (maps API available only on "official" Google accepted devices, Sprint Evo front facing camera...) and might require to be built within the system. Maybe some root privilege could help adding one, but this would have to be done on EACH device where applications using your library would want to run...