Cannot create variant 'classes' after configuration has been resolved error #2105
Comments
^ not sure if this means it's not really jib's fault? I suspect it has something to do with the It's hard for us to analyze this issue without a sample project from you. Can you provide us with a minimal example that recreates this? |
|
This seems unrelated to Jib really. Looks like a Gradle configuration issue in the project setup. Closing due to inactivity. Feel free to re-open if this is still an issue. |
|
I get the same error in JIB itself when Gradle version (in |
|
@dubinsky Can you provide a bit more information on what jib version you're using and whether you get the same issue when you use a Gradle version that's below |
|
@mpeddada1 I am using JIB from master; |
|
@chanseokoh oops, didn't see that :( |
|
Just FYI if it helps at all: if my memory serves me right, you can go ahead with upgrading to Gradle 6 (after applying |
|
@chanseokoh it should be possible to make the build compatible with Gradle 6 before dropping support for Gradle 5, but I understand ;) |
|
@chanseokoh thanks!!! |
Environment:
Description of the issue:
Build fails if the jibDockerBuild executed directly in the configured module. For example
./gradlew :my-module:jibDockerBuildIf the task executed from root i.e../gradlew jibDockerBuildit works normally.Expected behavior:
The task will work either way.
Steps to reproduce:
N/A
jib-gradle-pluginConfiguration:I am getting the same error with the jib configuration commented out. I.e. if the plugin is using the default configuration without the
jib { ... }block.Log output:
spoiler
Additional Information:
cache-infrain the stacktrace is a dependency of the project with the Jib plugin.The text was updated successfully, but these errors were encountered: