GitHub PushEvent at 2014-03-14 07:27:08
Repository: barclamp-pacemaker
Actor: vuntz
Payload: {"shas":[["89135c8c967ce704a4787f9253b8576871654921","a3b1ac66d44425905084924ee6cef90b31d2e761@suse.com","add rubydeps support for graphing class hierarchy\n\nhttps://github.com/dcadenas/rubydeps","Adam Spiers",true],["4d0496a90231de99104470e933fbadc34ccfdc5b","a3b1ac66d44425905084924ee6cef90b31d2e761@suse.com","prune class dependency tree\n\nChef::Mixin::Pacemaker::StandardCIBObject only requires\nPacemaker::CIBObject, not the whole hierarchy.","Adam Spiers",true],["fa05e437287f32fbcfc9779d597ed9e75257b2f1","a3b1ac66d44425905084924ee6cef90b31d2e761@suse.com","eliminate \"superclass mismatch for class Resource\" error\n\nPreviously libraries/pacemaker/mixins/resource_meta.rb had:\n\n  module Pacemaker\n    class Resource\n      module Meta\n        ...\n\nbut libraries/pacemaker/resource.rb had:\n\n  module Pacemaker\n    class Resource < Pacemaker::CIBObject\n      ...\n\nThis would work fine if libraries/pacemaker/resource.rb was loaded\nbefore libraries/pacemaker/mixins/resource_meta.rb, because then\nPacemaker::Resource would have Pacemaker::CIBObject as its parent class,\nand the mixin would simply add the Meta module within the existing\nPacemaker::Resource class.  However, due to Chef's somewhat erratic\nmethod of loading libraries, sometimes it could happen the other way\naround, in which case Pacemaker::Resource would be initially defined by\nthe mixin with no parent class, and then when resource.rb was loaded, it\nwould attempt to redefine Resource to have a parent class, triggering\nthe error.","Adam Spiers",true],["e184e12393533317465e936da33cfe451c207985","4342b29caadd28ff38359776cc35a8cfc392e9cf@gnome.org","Merge pull request #32 from aspiers/superclass-mismatch\n\nfix superclass mismatch","Vincent Untz",true]],"size":4,"ref":"refs/heads/release/roxy/master","head":"e184e12393533317465e936da33cfe451c207985"}