dependabot[bot] opened a new pull request #592: URL: https://github.com/apache/isis/pull/592
Bumps [jib-maven-plugin](https://github.com/GoogleContainerTools/jib) from 3.0.0 to 3.1.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/GoogleContainerTools/jib/releases";>jib-maven-plugin's releases</a>.</em></p> <blockquote> <h2>jib-maven-plugin v3.1.0</h2> <h3>Major Changes</h3> <ul> <li>For Google Artifact Registry (<code>*-docker.pkg.dev</code>), Jib now tries <a href="https://developers.google.com/identity/protocols/application-default-credentials";>Google Application Default Credentials</a> last like it has been doing for <code>gcr.io</code>. (<a href="https://github-redirect.dependabot.com/GoogleContainerTools/jib/pull/3241";>#3241</a>)</li> <li>Jib now creates an additional layer that contains two small text files: <a href="https://github.com/GoogleContainerTools/jib/tree/master/jib-maven-plugin/README.md#custom-container-entrypoint";><code>/app/jib-classpath-file</code> and <code>/app/jib-main-class-file</code></a>. They hold, respectively, the final Java runtime classpath and the main class computed by Jib that are suitable for app execution on JVM. For example, with Java 9+, setting the container entrypoint to <code>java --class-path @/app/jib-classpath-file @/app/jib-main-class-file</code> will work to start the app. (This is basically the default entrypoint set by Jib when the entrypoint is not explicitly configured by the user.) The files are always generated whether Java 8 or 9+, or whether <code>jib.container.entrypoint</code> is explicitly configured. The files can be helpful especially when setting a custom entrypoint for a shell script that needs to get the classpath and the main class computed by Jib, or f or <a href="https://github-redirect.dependabot.com/GoogleContainerTools/jib/issues/2471";>AppCDS</a>. (<a href="https://github-redirect.dependabot.com/GoogleContainerTools/jib/pull/3280";>#3280</a>)</li> <li>For Java 9+ apps, the default Java runtime classpath explicitly lists all the app dependencies, preserving the dependency loading order declared by Maven. This is done by changing the default entrypoint to use the new classpath JVM argument file (basically <code>java -cp @/app/jib-classpath-file</code>). As such, <code><container><expandClasspathDependencies></code> takes no effect for Java 9+. (<a href="https://github-redirect.dependabot.com/GoogleContainerTools/jib/pull/3280";>#3280</a>)</li> <li>Timestamps of file entries in a tarball built with <code>jib:buildTar</code> are set to the epoch, making the tarball reproducible. (<a href="https://github-redirect.dependabot.com/GoogleContainerTools/jib/issues/3158";>#3158</a>)</li> </ul> <p>See <a href="https://github.com/GoogleContainerTools/jib/blob/master/jib-maven-plugin/CHANGELOG.md";>CHANGELOG.md</a> for more details.</p> <h2>jib-gradle-plugin v3.1.0</h2> <h3>Major Changes</h3> <ul> <li>For Google Artifact Registry (<code>*-docker.pkg.dev</code>), Jib now tries <a href="https://developers.google.com/identity/protocols/application-default-credentials";>Google Application Default Credentials</a> last like it has been doing for <code>gcr.io</code>. (<a href="https://github-redirect.dependabot.com/GoogleContainerTools/jib/pull/3241";>#3241</a>)</li> <li>Jib now creates an additional layer that contains two small text files: <a href="https://github.com/GoogleContainerTools/jib/tree/master/jib-gradle-plugin/README.md#custom-container-entrypoint";><code>/app/jib-classpath-file</code> and <code>/app/jib-main-class-file</code></a>. They hold, respectively, the final Java runtime classpath and the main class computed by Jib that are suitable for app execution on JVM. For example, with Java 9+, setting the container entrypoint to <code>java --class-path @/app/jib-classpath-file @/app/jib-main-class-file</code> will work to start the app. (This is basically the default entrypoint set by Jib when the entrypoint is not explicitly configured by the user.) The files are always generated whether Java 8 or 9+, or whether <code>jib.container.entrypoint</code> is explicitly configured. The files can be helpful especially when setting a custom entrypoint for a shell script that needs to get the classpath and the main class computed by Jib, or for <a href="https://github-redirect.dependabot.com/GoogleContainerTools/jib/issues/2471";>AppCDS</a>. (<a href="https://github-redirect.dependabot.com/GoogleContainerTools/jib/pull/3280";>#3280</a>)</li> <li>For Java 9+ apps, the default Java runtime classpath explicitly lists all the app dependencies, preserving the dependency loading order declared by Gradle. This is done by changing the default entrypoint to use the new classpath JVM argument file (basically <code>java -cp @/app/jib-classpath-file</code>). As such, <code>jib.container.expandClasspathDependencies</code> takes no effect for Java 9+. (<a href="https://github-redirect.dependabot.com/GoogleContainerTools/jib/pull/3280";>#3280</a>)</li> <li>Timestamps of file entries in a tarball built with <code>jibBuildTar</code> are set to the epoch, making the tarball reproducible. (<a href="https://github-redirect.dependabot.com/GoogleContainerTools/jib/issues/3158";>#3158</a>)</li> <li>Added lazy evaluation for <code>jib.container.labels</code> using Gradle Property and Provider. (<a href="https://github-redirect.dependabot.com/GoogleContainerTools/jib/issues/3242";>#3242</a>)</li> </ul> <p>See <a href="https://github.com/GoogleContainerTools/jib/blob/master/jib-gradle-plugin/CHANGELOG.md";>CHANGELOG.md</a> for more details.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/GoogleContainerTools/jib/commits";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
