summaryrefslogtreecommitdiffstats
path: root/mobile/android/app/omnijar/build.gradle
diff options
context:
space:
mode:
Diffstat (limited to 'mobile/android/app/omnijar/build.gradle')
-rw-r--r--mobile/android/app/omnijar/build.gradle33
1 files changed, 0 insertions, 33 deletions
diff --git a/mobile/android/app/omnijar/build.gradle b/mobile/android/app/omnijar/build.gradle
deleted file mode 100644
index c5274a618..000000000
--- a/mobile/android/app/omnijar/build.gradle
+++ /dev/null
@@ -1,33 +0,0 @@
-buildDir "${topobjdir}/gradle/build/mobile/android/omnijar"
-
-apply plugin: 'java'
-
-// This project is a dummy project; the JAR produced is not used. The :app
-// project uses the set of inputs here to check if the omnijar needs to be
-// rebuilt. By listing them here as resource directories, IntelliJ labels each
-// checked directly nicely. Why list the directories here? There's a mismatch
-// between SourceDirectorySet and TaskInputs: the former is directory oriented,
-// while the latter is more general. That means its easy to convert this list
-// into inputs for :app, but not vice-versa. Sadly this implies that :app
-// evaluation depends on :omnijar, but the evaluation overhead is low enough
-// that we accept it.
-sourceSets {
- main {
- // Depend on the Gecko resources in mobile/android.
- resources {
- srcDir "${topsrcdir}/mobile/android/chrome"
- srcDir "${topsrcdir}/mobile/android/components"
- srcDir "${topsrcdir}/mobile/android/locales"
- srcDir "${topsrcdir}/mobile/android/modules"
- srcDir "${topsrcdir}/mobile/android/themes"
- srcDir "${topsrcdir}/toolkit"
- }
- }
-}
-
-apply plugin: 'idea'
-
-idea {
- module {
- }
-}