1. 16 Oct, 2014 2 commits
    • Brett Wooldridge's avatar
      Update HikariCP to 2.1.0, compile against the Java 6-compatible artifact · 9984939c
      Brett Wooldridge authored
      For those running applications on Java 8, dependency management for the
      Java 8-compatible artifact is also provided.
      
      Closes gh-1721
      9984939c
    • Andy Wilkinson's avatar
      Reinstate Bitronix's default server ID, provide property to override it · 01fd8cb8
      Andy Wilkinson authored
      Previously, Bitronix's server ID was hard-coded to be
      spring-boot-jta-bitronix. This created the possibility of multiple
      transaction managers performing recovery on each other's behalf as
      they would be unable to identify their own XIDs due to the common
      server ID.
      
      This commit reinstates the default (which is the IP address of the
      machine on which Bitronix is running), and introduces a new
      property, spring.jta.transaction-manager-id, that can be used to
      configure the id for both Atomikos and Bitronix. A cautionary note
      has also been added to the documentation for Atomikos and Bitronix
      explaining the need to configure this property.
      
      Closes gh-1548
      01fd8cb8
  2. 15 Oct, 2014 10 commits
  3. 14 Oct, 2014 7 commits
  4. 13 Oct, 2014 10 commits
    • Stephane Nicoll's avatar
      Fix typo · e60cc578
      Stephane Nicoll authored
      Fixes gh-1701
      e60cc578
    • Dave Syer's avatar
      Add org.hibernate.SQL to the --debug logger levels · 89197eb0
      Dave Syer authored
      I think this fixes gh-446 (it seems unreasonable to want to log the DDL
      even if it is not being executed)
      89197eb0
    • Andy Wilkinson's avatar
      Merge branch '1.1.x' · 2da4dc00
      Andy Wilkinson authored
      2da4dc00
    • Andy Wilkinson's avatar
      7060cc19
    • Andy Wilkinson's avatar
      Separate out the auto-configuration of Spring Data’s web support · 4b9f14f5
      Andy Wilkinson authored
      Previously, Spring Data’s web support was auto-configured as part of the
      JPA repositories auto-configuration. However, Spring Data’s web support
      isn’t dependent on the use of Spring Data JPA or even repositories.
      
      This commit moves the auto-configuration into a standalone class, making
      it independent of the use of Spring Data JPA and Spring Data
      repositories.
      
      Closes gh-1097
      4b9f14f5
    • Dave Syer's avatar
      Fix install command on Windows · f9010c18
      Dave Syer authored
      Windows absolute paths cannot be processed by the CLI compiler, so the install
      command wasn't working on Windows. This change converts ths path to a URI first
      and then it works as a Spring Resource.
      f9010c18
    • Andy Wilkinson's avatar
      Fix some grammar issues in docs · 72115719
      Andy Wilkinson authored
      Closes gh-1695
      72115719
    • Andy Wilkinson's avatar
      Merge branch '1.1.x' · 4308d111
      Andy Wilkinson authored
      4308d111
    • Eric Dahl's avatar
      Fix some grammar issues in docs · 16937746
      Eric Dahl authored
      16937746
    • Andy Wilkinson's avatar
      Fix ArrayStoreException caused by JerseyAutoConfiguration · 2b7bf3e7
      Andy Wilkinson authored
      JerseyAutoConfiguration is annotated with @ConditionalOnClass. It
      references both SpringComponentProvider.class and
      ServletRegistration.class. Normally, this wouldn't be a problem as, in
      the absence of either of those classes, the configuration class bean
      will not be present in the bean factory and, therefore, its
      annotations will never be introspected using reflection.
      
      However, JerseyAutoConfiguration is a WebApplicationInitializer. This
      means that when it's deployed to a standalone container,
      JerseyAutoConfiguration is found by the container and its class is
      passed to SpringServletContainerInitializer.
      SpringServletContainerInitializer introspects every
      WebApplicationInitializer class so that it can order them. This blows
      up if Jersey's SpringComponentProvider class isn't on the classpath as
      the annotation is referencing SpringComponentProvider as a Class and
      the attempt to load it fails. The problem can be avoided by
      referencing SpringComponentProvider using a String.
      
      Fixes gh-1696
      2b7bf3e7
  5. 11 Oct, 2014 1 commit
  6. 10 Oct, 2014 10 commits