diff options
| author | Chris Sarbora <sarbs@cyngn.com> | 2015-07-08 08:27:11 -0700 |
|---|---|---|
| committer | Chris Sarbora <sarbs@cyngn.com> | 2015-07-08 08:27:29 -0700 |
| commit | b1f4115b473570158091e71e71568d462631b7ce (patch) | |
| tree | b7e63250da062d351d854c41c74468e69288e4f8 /build/core | |
| parent | 71983e8a0a9b1c7cbf7303d6063ae0feefc15c8a (diff) | |
| download | vendor_replicant-b1f4115b473570158091e71e71568d462631b7ce.zip vendor_replicant-b1f4115b473570158091e71e71568d462631b7ce.tar.gz vendor_replicant-b1f4115b473570158091e71e71568d462631b7ce.tar.bz2 | |
Prevent Maven target from grabbing transitive dependencies
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
Diffstat (limited to 'build/core')
| -rw-r--r-- | build/core/maven_artifact.mk | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/build/core/maven_artifact.mk b/build/core/maven_artifact.mk index 2666b9c..3335353 100644 --- a/build/core/maven_artifact.mk +++ b/build/core/maven_artifact.mk @@ -41,7 +41,8 @@ $(LOCAL_PREBUILT_MODULE_FILE): -DoutputDirectory=$(dir $@) \ -Dmdep.prependGroupId=true \ -Dmdep.overWriteSnapshots=true \ - -Dmdep.overWriteReleases=true + -Dmdep.overWriteReleases=true \ + -Dtransitive=false @echo -e ${CL_GRN}"Download:"${CL_RST}" $@" include $(BUILD_PREBUILT) |