Datamapper DataMapper → 0.10.2

Comments and changes to this ticket

• 

  Dan Kubb (dkubb) September 5th, 2009 @ 04:43 PM

  • State changed from “new” to “confirmed”

  I'd like to see the rake -T output line up between extlib, data_objects, dm-core and dm-more (as close as possible, there are bound to be a few extra tasks in one project not in another).

  If the implementations were the same, or using shared core, or a packager (like jeweler) that would be ideal, but probably of secondary importance. Making the APIs consistent is the most important thing.

• 

  Dan Kubb (dkubb) November 6th, 2009 @ 02:08 AM

  • Assigned user set to “Alex Coles”

  Alex, I'm assigning this to you since you said you were going to refactor the Rakefiles for some of the projects.

  I don't know how many you want to do (I'm hoping extlib, data_objects, dm-core and dm-more), but even if you provide a good base on one of them it will provide enough direction for someone to continue your work.

• 

  Alex Coles November 6th, 2009 @ 09:43 AM

  • State changed from “confirmed” to “accepted”
• 

  Dan Kubb (dkubb) November 18th, 2009 @ 10:39 AM

  (from [9e7ddf4815fd71ae22abcc1412a83b2ad0e6b164]) Remove VERSION constants, requires from .gemspecs

  • use of require violates the gemspec spec.
  • this is a workaround until we move to Jeweler (or another solution) to make things work better with Bundler / allow for nightly builds.
  • platform-checking, File potentially also problematic.

  [#1023]

  Signed-off-by: Alex Coles alex@alexcolesportfolio.com
  http://github.com/datamapper/do/commit/9e7ddf4815fd71ae22abcc1412a8...

• 

  Alex Coles November 18th, 2009 @ 10:50 AM

  This is taking me longer than expected (for DataObjects). The current
  released version of Luis' rake-compiler does not work 100% with
  Jeweler "out of the box", so the need for some nasty workarounds:

  http://github.com/karottenreibe/rake-compiler/commit/93b800e9b5028e...

  The upside is that its forcing me to understand rake-compiler a little
  better. I probably will end up writing a Java version of
  rake-compiler, but in the meantime the Java equivalent tasks for
  compiling will start to follow how rake-compiler does things.

  The latest release of Jeweler also has problems with its the install
  tasks it creates (they don't install with the correct interpreter).
  This is fixed in their edge though.

• 

  Dan Kubb (dkubb) November 23rd, 2009 @ 06:23 AM

  (from [55b1d6dbc4cb910d60e1de1aad760ac79ed92544]) [data_objects][all java] Convert tasks to Jeweler

  • This is the "low-hanging fruit"... where we're just handling pure-Ruby or single platform(binary) gems, then porting is relatively straightforward. Multi-platform, multi-binary will require some work still to make the workflow work well.
  • Add metric and roodi tasks to data_objects.

  [#1023]

  Signed-off-by: Alex Coles alex@alexcolesportfolio.com
  http://github.com/datamapper/do/commit/55b1d6dbc4cb910d60e1de1aad76...

• 

  Alex Coles November 28th, 2009 @ 08:05 AM

  • Milestone set to “0.10.2”
• 

  Alex Coles November 30th, 2009 @ 02:21 PM

  • Tag cleared.
  • Title changed from “Rake tasks inconsistant” to “Rake tasks inconsistent”
• 

  Alex Coles November 30th, 2009 @ 02:21 PM

  • Tag set to “rake”
• 

  Alex Coles December 8th, 2009 @ 09:51 AM

  • State changed from “accepted” to “resolved”

  See commit 29a67ee.

  Rake tasks should now be consistent across the DataMapper family (extlib, do, dm-core, dm-more). Rake tasks have been cleaned up for DataObjects thanks to a new release of rake-compiler (0.7.0) which adds support for compiling Java extensions.

  Marking this as resolved.