1. 10 Mar, 2017 6 commits
  2. 09 Mar, 2017 8 commits
    • Stephane Nicoll's avatar
      Merge branch '1.4.x' into 1.5.x · 6624fe47
      Stephane Nicoll authored
      6624fe47
    • Stephane Nicoll's avatar
      Polish · e7922a57
      Stephane Nicoll authored
      e7922a57
    • Stephane Nicoll's avatar
      Merge branch '1.4.x' into 1.5.x · 207ab3ec
      Stephane Nicoll authored
      207ab3ec
    • Stephane Nicoll's avatar
      Make sure Hazelcast bootstraps before any JCache setup · 07c56c60
      Stephane Nicoll authored
      This commit makes sure that if a `javax.cache.CacheManager` is required,
      an auto-configured `HazelcastInstance` is fully resolved first. This
      prevents the case where the JCache bootstrap actually starts an instance
      early, followed by a second (potentially unwanted) instance created by the
      regular auto-configuration.
      
      Since the JCache implementation works with an `HazelcastInstance` behind
      the scenes, if there is one `HazelcastInstance` configured and it has a
      name, then we configure the `CacheProvider` to use that. Future Hazelcast
      version will allow to pass the instance directly (i.e. not requiring an
      actual name).
      
      Closes gh-8484
      07c56c60
    • Andy Wilkinson's avatar
      Merge branch '1.4.x' into 1.5.x · 50c0204f
      Andy Wilkinson authored
      50c0204f
    • Andy Wilkinson's avatar
      Correct the URL that's called to test servlet context resources · d32c3a7f
      Andy Wilkinson authored
      See gh-8299
      Closes gh-8525
      d32c3a7f
    • Andy Wilkinson's avatar
      Merge branch '1.4.x' into 1.5.x · 1395f38e
      Andy Wilkinson authored
      1395f38e
    • Andy Wilkinson's avatar
      Fix static resource handling when run in IDE or using Maven or Gradle · a2cf0455
      Andy Wilkinson authored
      The changes made for gh-8299 attempted to make static resource
      handling consistent across Jetty, Tomcat, and Undertow. They did so
      for application's launched using JarLauncher or WarLauncher but did
      not consider application's launched in an IDE or using spring-boot:run
      in Maven or bootRun in Gradle.
      
      Running in an IDE or via Maven or Gradle introduces two new
      resource locations:
      
       - Jars on the classpath with file protocol URLs (they are always
         jar protocol URLs when using either launcher)
       - Directories on the classpath from a project that is depended upon
         and contains resources in META-INF/resources
      
      This commit updates the factories for all three containers to handle
      these new resources locations. The integration tests have also been
      updated.
      a2cf0455
  3. 08 Mar, 2017 1 commit
  4. 07 Mar, 2017 2 commits
  5. 06 Mar, 2017 5 commits
  6. 03 Mar, 2017 14 commits
  7. 02 Mar, 2017 4 commits
    • Madhura Bhave's avatar
      Expose Health details if user has authority · d4b52a35
      Madhura Bhave authored
      If the Princial is a Spring Security Authentication object and the
      request doesn't have the right roles, check the authorities.
      
      Fixes gh-8471
      d4b52a35
    • Andy Wilkinson's avatar
      Merge pull request #8465 from Dave Syer · caefb234
      Andy Wilkinson authored
      * gh-8334:
        Polish "Allow loader.path to refer to nested jars"
        Allow loader.path to refer to nested jars
      caefb234
    • Andy Wilkinson's avatar
      Polish "Allow loader.path to refer to nested jars" · 6673d8ee
      Andy Wilkinson authored
      Closes gh-8334
      Closes gh-8465
      6673d8ee
    • Dave Syer's avatar
      Allow loader.path to refer to nested jars · 3701cce8
      Dave Syer authored
      Previously, each entry in loader.path could only refer to a standard
      jar file. Refering to such a jar would add all of the classes in
      the root of the jar to the class path.
      
      This commit adds support for referencing a directory within a jar file
      that contains one or more nested jars. For example:
      
      $ java -jar -Dloader.path='jar:file:./lib.jar/!BOOT-INF/lib' my.jar
      
      This will add all of the classes in all of that jars in the
      BOOT-INF/lib directory of lib.jar to the class path.
      
      See gh-8334
      3701cce8