Hi! I've also noticed this (weird) behaviour. I am planning an (huge) upgrade (from 0.25.x to 2.7.1) in all my puppet's boxes...
I've installed puppet's 2.7.1 gem and got a lot of "Could not find class" problem... and everything worked just fine with 0.25.x. So, I decided to uninstall the gem for version 2.7.1 and install puppet version 2.6.9. Everything worked just fine... no weird "Could not find class" problem... am I missing something? Thanks in advance, Gus On Jul 13, 11:03 am, Nigel Kersten <ni...@puppetlabs.com> wrote: > On Tue, Jul 12, 2011 at 11:29 PM, Peter Meier <peter.me...@immerda.ch>wrote: > > > > > Puppet has quite a powerfull autoloading feature of classes and I think > > it can be seen as a general best practice to have one class in a file in > > its corresponding path on the filesystem. > > What he said. :) > > Life really does become a lot simpler if you avoid 'import' everywhere you > can and just rely upon the class autoloader. > > -- > Nigel Kersten > Product Manager, Puppet Labs > Twitter: @nigelkersten > > *Join us for **PuppetConf *<http://www.bit.ly/puppetconfsig> > September 22nd and 23rd in Portland, Oregon, USA. > * > * -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
