also wanted to know whether there would be any issues
bcos of using a gem as a plugin or is it perctecly ok to do it.
I think the answer to your question is probably yes, using a gem as a plugin
would probably cause issues. Gems and Plugins have separate purposes. Gems
extend Ruby. Plugins extend Rails. They're put in separate places because
Ruby and Rails search for extensions in different places.
Aside from that... what is it you're trying to accomplish? If you already
have the functionality you're looking for as a gem, why would you want to
move that to a plugin?
hi bill i was actually looking for this when i came across the haml
plugin.
initially it was available as plugin and also as gem and i used it as
plugin
but now it has to be installed as gem and then we do a command which
copies a file to the plugin folder(dont know what we call doing this
technically).
then i learnt that i can copy the gem to vendor/plugins and it wud work
the same
so was looking for command
i am on rails 2.1.0 and it seems
the rake gems:unpack is the command i'm looking for but there seems to
be some rough edges with gem dependency things in rails 2.1.0. as per
the comments on this article by ryandaigle