The current version always redownloads the artifact.
Kali does not like the nested md5sum command and ignores it
leaving file checksum value blank so the test always fails.
A temporary variable is used to get around this limitation
of kali.
The echo "Downloading..." command has been modified to actually
print and has been moved so it only does so when downloading
the artifact.
Change-Id: I115860a87e55399a652d6548fe50f6204337f854
(cherry picked from commit 20c06fd75e09f3910ec699bdc54eec08f6bb4594)
* checksum will be downloaded and asserted to prevent a
redownload every clean
* Archives will exist (invisibly) at vendor/cm/prebuilt/archive
Change-Id: I637e86cacd146d665044a119885900dc4660e22b
Signed-off-by: Brandon McAnsh <brandon.mcansh@gmail.com>
* Gello being our first pawn
* Use curl instead of wget (more powerful)
* Ensure the intermediates directory exists prior to download
Change-Id: If19c18638a14a8b9ab55470ae6ee5a2deda2e3ec
Maven APK (Why are these in maven anyways?) will crash due to it not
needing to generate a jack file. This wasn't noticed before as brunch
succeeded, however, doing an mmm on one will cause this to fail. This
adds in logic to not generate a jack file for an apk in maven.
Change-Id: I44036bfd51ae3edd9437b153898b419ffc6ba2d6
Prebuilts weren't generating their .jack file when doing an mm or mmm
but would work with a brunch or full make. This makes it so mmm/mm
will properly generate it.
Change-Id: If5ccd1b557ef124b3c57fa09b172ec11caff886e
Now allows you to specify a target module to be
compiled prior to publish via LOCAL_MAVEN_TARGET_MODULE.
This utilizes the definition for intermediates-dir-for on
the target module after it sets an explicit dependency from
remote to local module.
Change-Id: I65b5e07fdcc3368e350b1935ccca381b74dce59e
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
