chiark / gitweb /
gradle: Never add lintOptions workaround
authorDaniel Martí <mvdan@mvdan.cc>
Thu, 24 Dec 2015 15:40:36 +0000 (16:40 +0100)
committerDaniel Martí <mvdan@mvdan.cc>
Thu, 24 Dec 2015 15:40:36 +0000 (16:40 +0100)
This breaks on newer plugin versions. Instead of complicating this logic
even further to support them, upstream devs should instead use gradle
configs that actually work.

If their build fails because of lint, it's theirs to fix, not ours.

fdroidserver/build.py

index 44d48bba93e3888e4bfa2617070830b1168dbb7c..d792132d570d42dbcbd2e87a36ad2c839c32b0ca 100644 (file)
@@ -736,11 +736,6 @@ def build_local(app, build, vcs, build_dir, output_dir, srclib_dir, extlib_dir,
     elif method == 'gradle':
         logging.info("Building Gradle project...")
 
-        # Avoid having to use lintOptions.abortOnError false
-        if build.gradlepluginver >= LooseVersion('0.7'):
-            with open(os.path.join(root_dir, 'build.gradle'), "a") as f:
-                f.write("\nandroid { lintOptions { checkReleaseBuilds false } }\n")
-
         cmd = [config['gradle']]
         if build.gradleprops:
             cmd += ['-P'+kv for kv in build.gradleprops]