1. 06 3月, 2019 1 次提交
  2. 03 11月, 2016 1 次提交
  3. 20 2月, 2016 1 次提交
  4. 24 9月, 2015 1 次提交
  5. 22 9月, 2015 1 次提交
  6. 11 9月, 2012 1 次提交
    • C
      Upgrade to JUnit 4.11 snapshot in support of JDK7 · dfe05305
      Chris Beams 提交于
      Class#getDeclaredMembers returns arbitrary results under JDK7. This
      results in non-deterministic execution of JUnit test methods, often
      revealing unintended dependencies between methods that rely on a
      specific order to succeed.
      
      JUnit 4.11 contains support for predictable test ordering [1], but at
      the time of this commit, JUnit 4.11 has not yet been released.
      Therefore we are testing against a snapshot version [2], which has been
      uploaded to repo.springsource.org [3] for easy access. Note that this
      artifact may be removed when JUnit 4.11 goes GA.
      
       - Care has been taken to ensure that spring-test's compile-time
         dependency on JUnit remains at 4.10. This means that the spring-test
         pom.xml will continue to have an optional <dependency> on JUnit
         4.10, instead of the 4.11 snapshot.
      
       - For reasons not fully understood, the upgrade to the 4.11 snapshot
         of junit-dep caused NoSuchMethodErrors around certain Hamcrest
         types, particularly CoreMatchers and Matchers. import statements
         have been updated accordingly throughout affected test cases.
      
       - Runtime errors also occurred around uses of JUnit @Rule and
         ExpectedException. These have been reverted to use simpler
         mechanisms like @test(expected) in the meantime.
      
       - Some test methods with order-based dependencies on one another have
         been renamed in order to fall in line with JUnit 4.11's new method
         ordering (as opposed to actually fixing the inter-test
         dependencies). In other areas, the fix was as simple as adding a
         tearDown method and cleaning up state.
      
       - For no apparent reason, the timeout in AspectJAutoProxyCreatorTests'
         testAspectsAndAdvisorNotAppliedToPrototypeIsFastEnough method begins
         to be exceeded. Prior to this commit the timeout value was 3000 ms;
         on the CI server under Linux/JDK6 and JDK7, the test begins taking
         anywhere from 3500-5500 ms with this commit. It is presumed that
         this is an incidental artifact of the upgrade to JUnit 4.11. In any
         case, there are no changes to src/main in this commit, so this
         should not actually represent a performance risk for Spring
         Framework users. The timeout has been increased to 6000 ms to
         accommodate this situation.
      
      [1]: https://github.com/KentBeck/junit/pull/293
      [2]: https://github.com/downloads/KentBeck/junit/junit-dep-4.11-SNAPSHOT-20120805-1225.jar
      [3]: https://repo.springsource.org/simple/ext-release-local/junit/junit-dep/4.11.20120805.1225
      
      Issue: SPR-9783
      dfe05305
  7. 31 1月, 2012 1 次提交
    • C
      Rename modules {org.springframework.*=>spring-*} · 02a4473c
      Chris Beams 提交于
      This renaming more intuitively expresses the relationship between
      subprojects and the JAR artifacts they produce.
      
      Tracking history across these renames is possible, but it requires
      use of the --follow flag to `git log`, for example
      
          $ git log spring-aop/src/main/java/org/springframework/aop/Advisor.java
      
      will show history up until the renaming event, where
      
          $ git log --follow spring-aop/src/main/java/org/springframework/aop/Advisor.java
      
      will show history for all changes to the file, before and after the
      renaming.
      
      See http://chrisbeams.com/git-diff-across-renamed-directories
      02a4473c
  8. 10 2月, 2011 1 次提交
  9. 03 1月, 2011 1 次提交
    • C
      M1 cut of environment, profiles and property work (SPR-7508) · b3ff9be7
      Chris Beams 提交于
      Decomposed Environment interface into PropertySources, PropertyResolver
      objects
      
          Environment interface and implementations are still present, but
          simpler.
      
          PropertySources container aggregates PropertySource objects;
          PropertyResolver provides search, conversion, placeholder
          replacement. Single implementation for now is
          PropertySourcesPlaceholderResolver
      
      Renamed EnvironmentAwarePropertyPlaceholderConfigurer to
      PropertySourcesPlaceholderConfigurer
      
          <context:property-placeholder/> now registers PSPC by default, else
          PPC if systemPropertiesMode* settings are involved
      
      Refined configuration and behavior of default profiles
      
          See Environment interface Javadoc for details
      
      Added Portlet implementations of relevant interfaces:
      
          * DefaultPortletEnvironment
          * PortletConfigPropertySource, PortletContextPropertySource
          * Integrated each appropriately throughout Portlet app contexts
      
      Added protected 'createEnvironment()' method to AbstractApplicationContext
      
          Subclasses can override at will to supply a custom Environment
          implementation.  In practice throughout the framework, this is how
          Web- and Portlet-related ApplicationContexts override use of the
          DefaultEnvironment and swap in DefaultWebEnvironment or
          DefaultPortletEnvironment as appropriate.
      
      Introduced "stub-and-replace" behavior for Servlet- and Portlet-based
      PropertySource implementations
      
          Allows for early registration and ordering of the stub, then
          replacement with actual backing object at refresh() time.
      
          Added AbstractApplicationContext.initPropertySources() method to
          support stub-and-replace behavior. Called from within existing
          prepareRefresh() method so as to avoid impact with
          ApplicationContext implementations that copy and modify AAC's
          refresh() method (e.g.: Spring DM).
      
          Added methods to WebApplicationContextUtils and
          PortletApplicationContextUtils to support stub-and-replace behavior
      
      Added comprehensive Javadoc for all new or modified types and members
      
      Added XSD documentation for all new or modified elements and attributes
      
          Including nested <beans>, <beans profile="..."/>, and changes for
          certain attributes type from xsd:IDREF to xsd:string
      
      Improved fix for detecting non-file based Resources in
      PropertiesLoaderSupport (SPR-7547, SPR-7552)
      
          Technically unrelated to environment work, but grouped in with
          this changeset for convenience.
      
      Deprecated (removed) context:property-placeholder
      'system-properties-mode' attribute from spring-context-3.1.xsd
      
          Functionality is preserved for those using schemas up to and including
          spring-context-3.0.  For 3.1, system-properties-mode is no longer
          supported as it conflicts with the idea of managing a set of property
          sources within the context's Environment object. See Javadoc in
          PropertyPlaceholderConfigurer, AbstractPropertyPlaceholderConfigurer
          and PropertySourcesPlaceholderConfigurer for details.
      
      Introduced CollectionUtils.toArray(Enumeration<E>, A[])
      
      Work items remaining for 3.1 M2:
      
          Consider repackaging PropertySource* types; eliminate internal use
          of SystemPropertyUtils and deprecate
      
          Further work on composition of Environment interface; consider
          repurposing existing PlaceholderResolver interface to obviate need
          for resolve[Required]Placeholder() methods currently in Environment.
      
          Ensure configurability of placeholder prefix, suffix, and value
          separator when working against an AbstractPropertyResolver
      
          Add JNDI-based Environment / PropertySource implementatinos
      
          Consider support for @Profile at the @Bean level
      
          Provide consistent logging for the entire property resolution
          lifecycle; consider issuing all such messages against a dedicated
          logger with a single category.
      
          Add reference documentation to cover the featureset.
      b3ff9be7
  10. 26 10月, 2010 1 次提交
    • C
      Merge 3.1.0 development branch into trunk · f480333d
      Chris Beams 提交于
      Branch in question is 'env' branch from git://git.springsource.org/sandbox/cbeams.git; merged into
      git-svn repository with:
      
          git merge -s recursive -Xtheirs --no-commit env
      
      No merge conflicts, but did need to
      
          git rm spring-build
      
      prior to committing.
      
      With this change, Spring 3.1.0 development is now happening on SVN
      trunk. Further commits to the 3.0.x line will happen in an as-yet
      uncreated SVN branch.  3.1.0 snapshots will be available
      per the usual nightly CI build from trunk.
      f480333d
  11. 27 10月, 2009 1 次提交
  12. 31 10月, 2008 1 次提交
  13. 29 10月, 2008 1 次提交