You shouldn't need to do anything, beyond some documentation to remind you (or others) that they need to install paperclip as well as your plugin.
The lib directories of all plugins are available before any plugin's init.rb is evaluated, so your code should be able to refer to classes in other plugins without having to do anything special. You could certainly add a 'require "attachment"' statement somewhere in your code, just to be explicit. - James On Jun 14, 11:12 am, "Till B." <[email protected]> wrote: > Hi, > > I'd like to rewrite a plugin called paperclipped_assets that's based on > paperclip and provides a central model keeping all attachments. > Unfortunately I need to require the class Attachment.rb of paperclip in > paperclipped_assets, which results in the following error > > uninitialized constant HasPaperclippedAsset::InstanceMethods::Attachment > > Is there something like a plugin_require which I could use to make > paperclipped_assets know the paperclip classes? Or do I have to join the > plugins to achieve this? > > Thanks for your help! > > Best regards > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
