Kiwix:Android.ui.preparing files/fr

Vardy Thanks for your reply.


>FAILURE: Build failed with an exception. >* What went wrong: >Execution failed for task ':app:lintDebug'. > Lint found errors in the project; aborting build.

 Fix the issues identified by lint, or create a baseline to see only new errors:
 ```

>Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0. > android { > lint { > baseline = file("lint-baseline.xml") > } > }


This suggestion always comes whenever lint is failing on something, it point us to make a lint-basline.xml file and suppress the lint on particular error.


>butterknife.lint.LintRegistry in /home/runner/.gradle/caches/transforms->3/f7c28b3d38f993a93532a66f30e0cd1b/transformed/jetified-butterknife-runtime->10.2.3/jars/lint.jar does not specify a vendor; see IssueRegistry#vendor


Good point we fix this asap.

and the above warnings is deprecation warning we are working on it to remove deprecated methods from our whole project.


Last time you point out the wrong translation in english string file. we had fixed it https://github.com/kiwix/kiwix-android/pull/3263 , now we can use ellipsis character instead of ... ?

MohitMali (talk)08:46, 15 March 2023

Actually no: don't you see the message "Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0".

Such Lint warnings should NOT be treated as "errors".

You still need to fix the incompatibility because you use "deprecated" Gradle features. Gradle 8.0 defines more precise rules that can correctly manage the various levels of messages emitted by various Linter tools. May be you started with a version of Gradel that did not complain, but Gradle 8.0 has new requirements and cannot correctly guess what is a blocking error or an informative warning without configuration because the current configuration is too weak, and cannot differentiate different messages emitted by your linter tool, possibly because your Linter tool uses some ambiguous "generic" syntax (e.g. some regexp) from which the effective severity cannot be assessed automatically. The suggested "lint-baseline.xml" configuration allows you to manage such filters or regexps for more precise assessment. By default, the generic rule many treat many (possibly all) warning as errors, and this is bad behavior only because you've not configured it correctly as instructed by Gradle 8.0.

The following links may help you:

Verdy p (talk)12:02, 15 March 2023