coderfromhere

I've updated the plugin to `v1.3.4` and I'm now able to run the java versions of the commands, but unfortunately the layout is still the same and it's missing the...

@sideeffffect at this point it's more about image layout parity between Gradle/Maven and sbt plugins. I'm in the process of migrating a project from Gradle/Java to sbt/Scala and it'd help...

As far as I understand the Gradle plugin's motivation for these meta-files, they allow custom user-defined entrypoints to remain stable and resistant to any potential future layout changes that jib...

Sure, `/app/jib-classpath-file` looks like a colon-separated list of image-included libraries and resources that the project depends on: ``` /app/resources:/app/classes:/app/libs/commons-logging-1.2.jar:/app/libs/xml-apis-1.4.01.jar:/app/libs/ion-java-1.0.2.jar:/app/libs/joda-time-2.8.1.jar[: ...] ``` and `/app/jib-main-class-file` contains the module path to the main...

And it seems like this is the PR that introduced these files into the plugin, serving the need of determinism in loading order: https://github.com/GoogleContainerTools/jib/pull/3280

Oh, that's a bummer, especially the lack of technical clarity on why not publishing it.