Issue #4178 has been updated by Markus Roberts. Status changed from Accepted to Closed
Cleaned up version with Luke's suggested refinement (use file globing rather than searching for each supported extension in turn), tests, and code simplifications pushed to master as commit:3c0059195fb2b1255f368d98021f4a99ecd121a6. ---------------------------------------- Bug #4178: Ruby manifests don't autoload http://projects.puppetlabs.com/issues/4178 Author: Luke Kanies Status: Closed Priority: High Assigned to: Markus Roberts Category: Target version: 2.6 Affected version: 2.6alpha1 Keywords: Branch: luke/tickets/master/4178-ruby_manifests_not_autoloading Discovered this while writing up the release notes. :/ Basically, it works fine if you use 'puppet <manifest>.rb', but doesn't if you throw the ruby file in a module and try to autoload it or, I think, import it. I've got code that fixes it, but it's not yet thoroughly tested; I'll post once I have a ticket number. -- 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.
