Issue #5719 has been updated by Luke Kanies.
I don't see any reason to complicate this that much. There's essentially no behavior difference between using 'module' and 'class' here except that one means you can't load Puppet and one does. It'd be awesome to have great APIs that meant we didn't have to load both projects at the same time once in a while, but even then, having code that specifically forbade that would still be silly. In the meantime, it's an absolute requirement for anything that doesn't have an API in the Dashboard, which today is far too much. ---------------------------------------- Bug #5719: Dashboard tries to declare Puppet::Resource as a module https://projects.puppetlabs.com/issues/5719 Author: Luke Kanies Status: Accepted Priority: Normal Assignee: Category: Target version: Keywords: Branch: Affected URL: Affected Dashboard version: This makes it so you can't load both Puppet and Dashboard at the same time. It's an easy fix: <pre> diff --git a/lib/puppet/report.rb b/lib/puppet/report.rb index 37ec1de..d13a7ec 100644 --- a/lib/puppet/report.rb +++ b/lib/puppet/report.rb @@ -58,7 +58,7 @@ module Puppet #:nodoc: end end - module Resource + class Resource class Status end end </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
