Dependencies of Maven targets will have to be managed manually. The prebuilt
target that the Maven target is based off of wasn't designed to handle multiple
artifacts per project. Additionally, this target is mainly intended for grabbing
APKs or other standalone blobs, not for pulling in a full jar dependency tree.
If that is your use case, you may want to investigate simply converting your
project to Gradle (or the Maven build system, if you can stomach it).
Change-Id: Iaf48c95c704cfdc85e0074394ff3c7464937e60c
Change-Id: If62e6b1d2ac41730ff2a8d562173abd2cb768f93
Add cmstatusbar service to system server services context
Change-Id: I77c5de75722cc5f36a5326e3da57ab661b89d189
Build Platform resource package.
Change-Id: Id60f66b6db23989db1472a19bcb079b0083f7393
vendor/cm: Lock cm platform library/cmsdk to non-release builds.
Change-Id: I01c1c3fe559d438e28339ce426d7ba7e42724002
* vendor/*/build/core/definitions.mk is automatically sourced by the
build system to load custom macros. Start using this for some
of our own.
* Adds a "uniq" macro to remove duplicates from a list without changing
it's order.
Change-Id: Id5f1eb4b9f81bb31ca0b3d5e74c298b3d105da10
Chris Sarbora
Adnan Begovic
Steve Kondik