Questions: 1. Is it OK that I change all the `compile` to `implementation` (and `testCompile` to `...

# gradle

[pawel.barszcz]

Questions:
1. Is it OK that I change all the compile to implementation (and testCompile to testImplementation)? Did I understand gradle output correctly with its deprecation warning?
2. What is the proper configuration to have library in B avaiable in A too? (if A is including B, and as we know from Gradle output, compile is deprecated)
3. Is there any place where I can read about currently supported configurations and what is the result of using them?

[mkobit]

pawel.barszcz: it sounds like you want the api configuration

[mkobit]

And should use the java-library plugin

[pawel.barszcz]

Would it be OK to have both kotlin and java-library applied? Is that plugin doing something more w/o applying `implementation`/`api` configuration or is just providing such configs (in other words: would it affect build somehow even without api configuration being used?) And, as I understand, it would be OK to use that java-library in all child projects of my whole project. I mean in all modules like persistence, domain, http-client etc. and to not use it in my two “end-side” projects: runner (Spring Boot) and integration-tests.

[pawel.barszcz]

especially this point looks not so nice: https://docs.gradle.org/current/userguide/java_library_plugin.html#sec:java_library_known_issues_compat

[mkobit]

kotlin and java-library should be good together (I haven't verified.it deeply yet) The java-library plugin is pretty thin https://github.com/gradle/gradle/blob/master/subprojects/plugins/src/main/java/org/gradle/api/plugins/JavaLibraryPlugin.java