krs-world
commented
4 years ago If you understand all fo this, can you do a major surgery on build.gradle and give the rest of us a brief tutorial. I find this language so dense. I am sure there are lots of stuff that are unused in that file.
-- krs
On 3/23/20 12:42 PM, Alec Goncharow wrote:
We need to clean up the |build.gradle| file before we run into some annoying problems,
❯ gradle fatjar --warning-mode all
Configure project: The maven plugin has been deprecated. This is scheduled to be removedin Gradle 7.0. Please use the maven-publish plugin instead. Consult the upgrading guidefor further information: https://docs.gradle.org/6.2.2/userguide/upgrading_version_5.html#legacy_publication_system_is_deprecated_and_replaced_with_the_publish_plugins at build_bljv8pmkjohslkqeynovqm379.run(/home/alec/bridges/bridges/build.gradle:15) (Run with --stacktrace to get the full stack trace of this deprecation warning.) The AbstractArchiveTask.version property has been deprecated. This is scheduled to be removedin Gradle 7.0. Please use the archiveVersion property instead. See https://docs.gradle.org/6.2.2/dsl/org.gradle.api.tasks.bundling.AbstractArchiveTask.html#org.gradle.api.tasks.bundling.AbstractArchiveTask:versionfor more details. at build_bljv8pmkjohslkqeynovqm379$_run_closure6$_closure14.doCall(/home/alec/bridges/bridges/build.gradle:98) (Run with --stacktrace to get the full stack trace of this deprecation warning.) The AbstractArchiveTask.baseName property has been deprecated. This is scheduled to be removedin Gradle 7.0. Please use the archiveBaseName property instead. See https://docs.gradle.org/6.2.2/dsl/org.gradle.api.tasks.bundling.AbstractArchiveTask.html#org.gradle.api.tasks.bundling.AbstractArchiveTask:baseNamefor more details. at build_bljv8pmkjohslkqeynovqm379$_run_closure6.doCall(/home/alec/bridges/bridges/build.gradle:101) (Run with --stacktrace to get the full stack trace of this deprecation warning.) The compile configuration has been deprecatedfor dependency declaration. This will fail with an error in Gradle 7.0. Please use the implementation configuration instead. Consult the upgrading guidefor further information: https://docs.gradle.org/6.2.2/userguide/upgrading_version_5.html#dependencies_should_no_longer_be_declared_using_the_compile_and_runtime_configurations at build_bljv8pmkjohslkqeynovqm379$_run_closure9.doCall(/home/alec/bridges/bridges/build.gradle:169) (Run with --stacktrace to get the full stack trace of this deprecation warning.) The compile configuration has been deprecatedfor resolution. This will fail with an error in Gradle 7.0. Please resolve the compileClasspath configuration instead. Consult the upgrading guidefor further information: https://docs.gradle.org/6.2.2/userguide/upgrading_version_5.html#dependencies_should_no_longer_be_declared_using_the_compile_and_runtime_configurations at build_bljv8pmkjohslkqeynovqm379$_run_closure6$_closure15.doCall(/home/alec/bridges/bridges/build.gradle:102) (Run with --stacktrace to get the full stack trace of this deprecation warning.)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/BridgesUNCC/bridges-java/issues/155, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLFEOFO4KEZPPN5TRJCXWTRI6GNZANCNFSM4LSAJNHA.
--
Kalpathi Subramanian Ph: 704 687 8579 Associate Professor Email: krs@uncc.edu Dept of Computer Science Web:http://webpages.uncc.edu/krs The University of North Carolina Charlotte, NC 28202-0001
We need to clean up the
build.gradlefile before we run into some annoying problems,