title: SIngle jar startup failed after upgrade from Spring Boot 1.3.7 to 1.4.0
body: <p>After upgrading from Spring Boot 1.3.7 to 1.4.0 we can no longer start our application as a single jar build with the Spring Boot Maven plugin. Our application is a small REST interface using Jersey and Jetty. We use Maven and our pom file is pretty standard Spring Boot.</p>
  
  <p>We can still run the application using <code>mvn spring-boot:run</code> and from within Eclipse, but when run as a single jar Jersey <code>ResourceFinder</code> complains that it cannot find <code>.jar!/BOOT-INF/classes</code>.</p>
  
  <p>When I unpack the jar the folder <code>BOOT-INF/classes</code> is present and contains the expected classes and resources.</p>
  
  <p>Any help appreciated.</p>
  
  <pre><code>2016-08-10 14:58:31.162 ERROR 16071 --- [           main] o.s.boot.SpringApplication               
  : Application startup failed
  
  org.springframework.beans.factory.BeanCreationException: 
  Error creating bean with name 'jerseyConfig' defined in URL
  [jar:file:/acmesource/acme/acme-core/acme-core-api/target/acme-core-api-0.1
  SNAPSHOT.jar!/BOOT-INF/classes!/com/acme/core/api/JerseyConfig.class]: Bean 
  instantiation via constructor failed; nested exception is 
  org.springframework.beans.BeanInstantiationException: Failed to instantiate 
  [com.acme.core.api.JerseyConfig]: Constructor threw exception; nested 
  exception is
  org.glassfish.jersey.server.internal.scanning.ResourceFinderException:
  java.io.FileNotFoundException: /acmesource/acme/acme-core/acme-core
  api/target/acme-core-api-0.1-SNAPSHOT.jar!/BOOT-INF/classes (No such file or directory)
  </code></pre>