On Dec 19, 2010, at 1:37 AM, Ken Barber wrote: > Would be terrible - because I would lose the arguments if the package was > defined elsewhere earlier. That would be dumb. Also - the reverse is true ... > by defining your own package you may be ruining someone else's package > definition which defines arguments. Like you say - the ordering can cause > problems. > > FYI - The use-case where I would use the if !defined methodology would be > when you are defining a re-usable module that you know may (but not always) > conflict with another. Nothing is a silver bullet it seems in puppet, and I > have had to use this method at least once or twice to avoid stepping on > pre-existing content that I can't influence :-).
Ya. This is what I meant. Thanks for explaining. For the original example, it's just easier to create a tomcat class that has the packages and then include the tomcat class in both service classes. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
