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
The boot jars produced by the Gradle plugin injects the launcher classes first, violating an implicit specification discussed here and in JarInputStream:
public JarInputStream(InputStream in, boolean verify) throws IOException {
super(in);
this.doVerify = verify;
// This implementation assumes the META-INF/MANIFEST.MF entry
// should be either the first or the second entry (when preceded
// by the dir META-INF/). It skips the META-INF/ and then
// "consumes" the MANIFEST.MF to initialize the Manifest object.
In our case we're indexing jars from in a context where we don't have random access to the file, so that implicit contract makes it easy to know if we can expect a manifest or if we need to fallback, but it's not possible for these jars:
wilkinsona
changed the title
Spring Boot launcher jars invalid for some cases
Gradle plugin creates fat jars that do not align with assumption that META-INF/MANIFEST.MF should be the first or second entry
May 2, 2019
wilkinsona
changed the title
Gradle plugin creates fat jars that do not align with assumption that META-INF/MANIFEST.MF should be the first or second entry
Gradle plugin creates fat jars that do not align with unspecified assumption that META-INF/MANIFEST.MF should be the first or second entry
May 2, 2019
The boot jars produced by the Gradle plugin injects the launcher classes first, violating an implicit specification discussed here and in
JarInputStream
:https://bugs.openjdk.java.net/browse/JDK-8031748
In our case we're indexing jars from in a context where we don't have random access to the file, so that implicit contract makes it easy to know if we can expect a manifest or if we need to fallback, but it's not possible for these jars:
In the meantime we're going to have our code check for this case specifically.
The text was updated successfully, but these errors were encountered: