bisq/gradle.properties

systemProp.org.gradle.internal.http.connectionTimeout=120000
systemProp.org.gradle.internal.http.socketTimeout=120000

# Makes Y/N user prompts more readable during installer packaging
org.gradle.console=plain

org.gradle.dependency.verification.console=verbose
Increase Gradle HTTP timeouts from 30 => 120 seconds Problem: Gradle's default 30 second HTTP timeouts often cause bisq-* component builds to fail when resolving dependencies built on the fly via JitPack, e.g.: https://travis-ci.org/bisq-network/bisq-core/builds/356777615#L518-L525. Solution: Increase timeout values to 120 seconds, which should be more that sufficient. See: - gradle/gradle#3370 - gradle/gradle#3371 - gradle/gradle#4629 2018-03-22 10:39:52 +01:00			`systemProp.org.gradle.internal.http.connectionTimeout=120000`
			`systemProp.org.gradle.internal.http.socketTimeout=120000`
Build: Change default console to plain Change default gradle console style to plain. This makes y/n user prompts more readable during installer packaging, without having to specify --console=plain. 2021-05-24 09:13:36 +02:00
			`# Makes Y/N user prompts more readable during installer packaging`
			`org.gradle.console=plain`
2nd attempt at a tiny daonode rest service Based on chimp1984's https://github.com/bisq-network/bisq/pull/6184 2022-05-07 18:37:42 -03:00
Reenable verbose dependency verification (failure report) The built-in Gradle dependency verification XML writer does not find all our libraries for some unknown reason. I had to compute and add multiple hashes manually. It seems like it is OS related and the CI output helped to fix the problem. The console output makes it hard to fix issues because we cannot access the generated HTML file. This change reenables the verbose failure report. 2022-12-06 20:18:22 +01:00			`org.gradle.dependency.verification.console=verbose`