Adding upstream version 86.0.1.upstream/86.0.1upstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 34 insertions, 0 deletions

diff --git a/mobile/android/app/omnijar/build.gradle b/mobile/android/app/omnijar/build.gradle
new file mode 100644
index 0000000000..10a61d7975
--- /dev/null
+++ b/mobile/android/app/omnijar/build.gradle
@@ -0,0 +1,34 @@
+buildDir "${topobjdir}/gradle/build/mobile/android/omnijar"
+
+apply plugin: 'java'
+
+// This project is a dummy project; the JAR produced is not used.  The root
+// 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 the root project, but not vice-versa.  Sadly this would mean
+// that the root project evaluation depends on :omnijar, so we duplicate in the
+// root project.
+sourceSets {
+    main {
+        // These are supposed to be files that go into the omnijar.  But yes,
+        // toolkit/ has lots of native code.
+        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 {
+    }
+}