15

My current jar in build.gradle is like below:

jar {
manifest {
    attributes "Main-Class": "hoge.Main"
}
    from configurations.compile.collect { it.isDirectory() ? it : zipTree(it) }
}

and working well.

However, I have a message from Gradle (maybe since 6+?)

This is the actual message:

The compile configuration has been deprecated for dependency declaration. This will fail with an error in Gradle 7.0. Please use the implementation configuration instead.

The part configurations.compile is deprecated.

How can I update it?

If I changed 

jar {
manifest {
    attributes "Main-Class": "hoge.Main"
}
    from configurations.implementation.collect { it.isDirectory() ? it : zipTree(it) }
}

Gradle says > Resolving configuration 'implementation' directly is not allowed

kensuke1984
  • 949
  • 1
  • 11
  • 21

4 Answers4

12

You need to replace compile by runtimeClasspath in your case.

In previous Gradle versions, compile had too many responsibilities:

  • Declare dependencies
  • Resolved as the compile classpath
  • Exposed to consuming projects

It has been replaced by implementation for dependency declaration, it also needs to be replaced by something for resolution.

However in your case, you most likely want to package the runtime dependencies and not the compile ones. Hence you should use runtimeClasspath as the configuration to resolve. And not compileClasspath which would not contain any runtimeOnly dependencies.

Louis Jacomet
  • 13,661
  • 2
  • 34
  • 43
11

For others wanting to upgrade their Gradle configuration to the 7.0+ format, note that simply replacing compile with implementation or api will likely bug out if you use the java plugin. You need to be using the java-library plugin. Documentation.

Make sure that in your gradle.config you replace:

apply plugin: 'java'

with:

apply plugin: 'java-library'

You use implementation for non-transitive dependencies, and api for transitive ones (if the dependencies are consumed directly by dependents of your project).

Andrei
  • 1,723
  • 1
  • 16
  • 27
4

The compile configuration has been deprecated in favor of implementation.

See docs.

smac89
  • 39,374
  • 15
  • 132
  • 179
  • 4
    I know it. I asked how to update my code for the deprecation. – kensuke1984 Dec 17 '19 at 05:26
  • 1
    @kensuke1984 How to do it is to replace all use of `compile` with `implementation` – smac89 Dec 17 '19 at 05:27
  • 3
    yeah Thank you but when I did it, I have "> Resolving configuration 'implementation' directly is not allowed" – kensuke1984 Dec 17 '19 at 05:34
  • @kensuke1984 you are now asking a new question. See https://stackoverflow.com/questions/47910578/not-able-to-copy-configurations-dependencies-after-upgrading-gradle-plugin-for-a – smac89 Dec 17 '19 at 05:40
  • `compile` to `implementation` has been a major change. – Vishwa Ratna Dec 17 '19 at 05:44
  • Thanks... https://imperceptiblethoughts.com/shadow/ I finally use it. I wonder if there are ways to simply do this kind of things without importing it. – kensuke1984 Dec 17 '19 at 06:16
0

May help others. Got this to work by using java-library plugin and as mentioned in https://docs.gradle.org/current/userguide/java_library_plugin.html runtimeClassPath is not consumable but resolvable. First level dependencies could be collected like : def firstLevelDepdendencies = project.configurations.runtimeClassPath.resolvedConfiguration.firstLevelModuleDependencies.collectMany { it.moduleArtifacts }.toSet()

Deepa Ravi
  • 1