1. 09 May, 2014 6 commits
  2. 08 May, 2014 23 commits
  3. 07 May, 2014 10 commits
    • Andy Wilkinson's avatar
      Upgrade to AspectJ 1.8.0 · e7b2fc5f
      Andy Wilkinson authored
      Upgrade to latest version of AspectJ and provide dependency management
      for all of its modules.
      e7b2fc5f
    • Dave Syer's avatar
      Initialize logback is it is present in CLI · 894482df
      Dave Syer authored
      This (empirically) fixes gh-726 using a new utility
      (LogbackInitializer) in the loader tools. If anyone has enough
      Gradle fu to understand where to put it (after the classpath is established
      but before compilation) we could do the same thing in the Gradle plugin
      (and that would fix gh-724).
      894482df
    • Stephane Nicoll's avatar
      Fix dependency management failure · 1ef3d3bd
      Stephane Nicoll authored
      All dependencies have recently moved to the spring-boot-dependencies
      POM but that POM does not contain the repositories that are required to
      download milestone artifacts.
      
      This commit moves the default profile that is active by default at the
      right place in the hierarchy so that it is applied there as well.
      1ef3d3bd
    • Andy Wilkinson's avatar
      Upgrade to the Spring Data Dijkstra release train · 62ac51ee
      Andy Wilkinson authored
      In addition to the upgrade to Dijkstra (#743) Spring HATEOAS has been
      upgraded to 0.11.0 (#801) and Mongo's Java driver has been upgraded to
      2.12.1 (#689). In both cases this is the same version as is used by
      Dijkstra RC1.
      
      The new version of Mongo's Java driver changes the exception that's
      thrown when Mongo isn't running and a connection attempt fails. The
      Mongo sample has been updated accordingly.
      
      RepositoryRestMvcAutoConfiguration has been updated to be configured
      before JpaRepositoriesAutoConfiguration. This ensures that the
      former's transitive import of SpringDataJacksonConfiguration takes
      precedence over the latter's import of the same. This is necessary as
      RepositoryRestMvcConfiguration requires a bean that's declared by
      SpringDataJacksonConfiguration and, if JpaRepositoriesAutoConfiguration
      is processed first, its conditions may cause the import
      SpringDataJacksonConfiguration to be skipped causing instantiation
      of RepositoryRestMvcConfiguration to fail.
      
      Closes #689
      Closes #743
      62ac51ee
    • Andy Wilkinson's avatar
      638561d8
    • Phillip Webb's avatar
      User hard-coded spring-boot.version · 75494d2f
      Phillip Webb authored
      Replace the `spring-boot.version` property with a hard-coded value,
      rather than relying on the parent version. Allows locally installed
      snapshots to be used as the parents of projects with a different version
      number.
      75494d2f
    • Phillip Webb's avatar
      Polish · 32d2fc25
      Phillip Webb authored
      32d2fc25
    • Andy Wilkinson's avatar
      Upgrade to Spring AMQP 1.3.2 · 1fc6bbda
      Andy Wilkinson authored
      Upgrade to latest release of Spring AMQP and provide dependency
      management for all of its modules
      
      Closes #799
      1fc6bbda
    • Greg Turnquist's avatar
      Upgrade to ActiveMQ 5.9.1 · 5eb08dc3
      Greg Turnquist authored
      Closes #397 and #717
      5eb08dc3
    • Dave Syer's avatar
      Add JPA to flyway sample · 9ba88cf6
      Dave Syer authored
      9ba88cf6
  4. 06 May, 2014 1 commit
    • Stephane Nicoll's avatar
      Exclude support in the maven plugin · 15501eaa
      Stephane Nicoll authored
      This commit provides several options to exclude one or more
      dependencies:
      
      * excludes allows to specify an arbitrary number of exclude sub
        element defining the groupId and artifactId of the dependency
        to exclude
      * excludedGroupIds defines the comma separated list of groupIds
        to exclude
      * excludeArtifactIds defines the comma separated list of artifactIds
        to exclude
      
      While any artifact can be excluded, this is designed to exclude
      provided-scoped dependencies that should not be bundled in the
      executable jar/war.
      
      The outcome of java -jar myapp.jar should be consistent with the run
      goal: these exclusions are therefore applied to the classpath that
      the run goal computes to launch the application.
      
      This commit also adds some integration tests and updates the
      plugin's documentation
      
      Fixes gh-649, gh-650 and gh-674
      15501eaa