You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating jib-maven-plugin from version 3.0.0 to version 3.1.0 execution of dockerBuild goal for container with container.entrypoint=INHERIT configuration option fails with error:
[ERROR] Failed to execute goal com.google.cloud.tools:jib-maven-plugin:3.1.0:dockerBuild (docker-image-package) on project javadocs: Main class was not found, perhaps you should add a `mainClass` configuration to jib-maven-plugin -> [Help 1]
README says that entrypoint=INHERIT means mainClass is not taken into account, which seems to be broken in 3.1.0
Expected behavior:
After updating 3.0.0 -> 3.1.0 build should succeed because release notes don't say anything about changed behaviour of entrypoint=INHERIT configuration.
Steps to reproduce:
Add jib-maven-plugin configuration from block below with version 3.0.0 into pom.xml:
Execute the following command: mvn package and Docker image is built successfully.
Change jib-maven-plugin version to 3.1.0, execute mvn package - build fails with the following error:
[ERROR] Failed to execute goal com.google.cloud.tools:jib-maven-plugin:3.1.0:dockerBuild (docker-image-package) on project javadocs: Main class was not found, perhaps you should add a `mainClass` configuration to jib-maven-plugin -> [Help 1]
[ERROR] Failed to execute goal com.google.cloud.tools:jib-maven-plugin:3.1.0:dockerBuild (docker-image-package) on project javadocs: Main class was not found, perhaps you should add a `mainClass` configuration to jib-maven-plugin -> [Help 1]
Additional Information:
The text was updated successfully, but these errors were encountered:
Environment:
Description of the issue:
After updating
jib-maven-plugin
from version3.0.0
to version3.1.0
execution ofdockerBuild
goal for container with container.entrypoint=INHERIT configuration option fails with error:README says that entrypoint=INHERIT means mainClass is not taken into account, which seems to be broken in 3.1.0
Expected behavior:
After updating 3.0.0 -> 3.1.0 build should succeed because release notes don't say anything about changed behaviour of entrypoint=INHERIT configuration.
Steps to reproduce:
Add
jib-maven-plugin
configuration from block below with version3.0.0
into pom.xml:Execute the following command:
mvn package
and Docker image is built successfully.Change
jib-maven-plugin
version to3.1.0
, executemvn package
- build fails with the following error:jib-maven-plugin
Configuration:Log output:
Additional Information:
The text was updated successfully, but these errors were encountered: