Commits on May 19, 2010
  1. Version bump to 1.0.0.rc1

    dkubb committed May 19, 2010
Commits on May 18, 2010
Commits on May 17, 2010
Commits on May 10, 2010
  1. Updated to the new property API

    solnic authored and dkubb committed May 6, 2010
  2. Implement validation error support in separate modules

    snusnu committed May 10, 2010
    This is still require order dependent. Currently,
    dm-validations need to be required before
    dm-serializer for serializing of ValidationErrors
    objects to work properly. This will be changed soon.
Commits on Apr 1, 2010
  1. [dm-more] Removed unnecessary :branch => 'master' from Gemfiles

    dkubb committed Apr 1, 2010
    * The master branch is the default branch anyway, so specifying this
      explicitly was redundant.
Commits on Mar 31, 2010
Commits on Mar 30, 2010
  1. DataMapper::Validate is now DataMapper::Validations

    snusnu committed Mar 30, 2010
    Since this change has the potential to completely
    break community plugins that rely on doing stuff
    like DataMapper.const_defined?('Validate'), we
    still provide a constant alias for the time being.
    will continue to work for some time but will not
    be supported once we hit 1.0. The release notes
    for the next release will include a warning that
    this namespace is deprecated and
    should be used instead. In fact, we might add API
    to dm-validations that will allow to check for its
    presence without the need of doing const_defined?
    Big thanks to hipe on IRC, for totally helping me
    out with the search/replace regex that made this
    refactoring bearable.
      search:  \b(Validate)($|:)
      replace: Validations$2
    While it didn't catch *all* occurrences, it only
    left out 3 places in the whole of dm-more. Note
    that it didn't touch comments that started with
      # Validate something for some reason
Commits on Mar 22, 2010
Commits on Mar 20, 2010
  1. [all] Only require the gem under test in spec_helpers

    snusnu committed Mar 17, 2010
    This will make sure that all the gems require
    everything they need to be fully functional.
  2. [all] require 'dm-core' if a dm constant is used

    snusnu committed Mar 16, 2010
    1) This is a workaround for current bundler which
       doesn't yet respect the order in which the gems
       have been declared in the Gemfile, when doing a
    2) Actually I also think it's good style to require
       all the code that we need in order to perform
       a task. Even if most applications will always
       require dm-core before requiring any of its
       plugins, it still doesn't hurt to be explicit
       and to avoid possible bugs in the first place.
Commits on Jan 27, 2010
Commits on Dec 30, 2009
Commits on Dec 12, 2009
  1. Removed rubyforge release task

    dkubb committed Dec 12, 2009
    * Moved task importing inside the Jeweler block
  2. [dm-more] Updated runtime and development gem dependencies

    dkubb committed Dec 12, 2009
    * Regenerated gemspecs
    * Minor path fixes for 1.9.2
    * Fixed failing specs for 1.9.2
Commits on Nov 30, 2009
  1. [dm-serializer] Added json_pure as a required dependency

    dkubb committed Nov 30, 2009
    * If native json gem is not installed, then json_pure will be
      used as a fallback.
    [#1137 state:resolved]
Commits on Nov 24, 2009
  1. [dm-more] Updated spec.opts to be consistent

    dkubb committed Nov 24, 2009
    * Added profile format
  2. [dm-more] Updated gemspecs

    dkubb committed Nov 24, 2009
  3. [dm-more] Converted to use Jeweler

    dkubb committed Nov 24, 2009
    * Removed old/unecessary files
Commits on Nov 20, 2009
Commits on Nov 11, 2009
  1. [dm-more] Updated to use :required instead of :nullable for Property …

    dkubb committed Nov 11, 2009