Executable Jar Restrictions

You need to consider the following restrictions when working with a Spring Boot Loader packaged application:

• Zip entry compression: The ZipEntry for a nested jar must be saved by using the ZipEntry.STORED method. This is required so that we can seek directly to individual content within the nested jar. The content of the nested jar file itself can still be compressed, as can any other entry in the outer jar.

• System classLoader: Launched applications should use Thread.getContextClassLoader() when loading classes (most libraries and frameworks do so by default). Trying to load nested jar classes with ClassLoader.getSystemClassLoader() fails. java.util.Logging always uses the system classloader. For this reason, you should consider a different logging implementation.

• Related Spring Documentation

• Spring Boot
• Spring Framework
• Spring Cloud
  • Spring Cloud Build
  • Spring Cloud Bus
  • Spring Cloud Circuit Breaker
  • Spring Cloud Commons
  • Spring Cloud Config
  • Spring Cloud Consul
  • Spring Cloud Contract
  • Spring Cloud Function
  • Spring Cloud Gateway
  • Spring Cloud Kubernetes
  • Spring Cloud Netflix
  • Spring Cloud OpenFeign
  • Spring Cloud Stream
  • Spring Cloud Task
  • Spring Cloud Vault
  • Spring Cloud Zookeeper
• Spring Data
  • Spring Data Cassandra
  • Spring Data Commons
  • Spring Data Couchbase
  • Spring Data Elasticsearch
  • Spring Data JPA
  • Spring Data KeyValue
  • Spring Data LDAP
  • Spring Data MongoDB
  • Spring Data Neo4j
  • Spring Data Redis
  • Spring Data JDBC & R2DBC
  • Spring Data REST
• Spring Integration
• Spring Batch
• Spring Security
  • Spring Authorization Server
  • Spring LDAP
  • Spring Security Kerberos
  • Spring Session
  • Spring Vault
• Spring AI
• Spring AMQP
• Spring CLI
• Spring GraphQL
• Spring for Apache Kafka
• Spring Modulith
• Spring for Apache Pulsar
• Spring Shell All Docs...