Where oh where are my rails plugins?

Posted by Dr Nic on July 11, 2007 and blessed with 8 comments

I can’t be the only person to notice the disappearance of old faithful plugins like simply_helpful and others.

They got deprecated. Enough of their code is now in rails edge that if you’re on rails edge you don’t ever need the plugins.

Great.

Um, except not on rails edge. That is, new apps using 1.2.3, or old apps where you’ve imported the plugin via piston and now piston is spitting the dummy that the original svn url is wrong.

Josh Peek Josh Knowles [via ticket] educated me to their new hide-y-hole in the plugin legacy list (svn list http://svn.rubyonrails.org/rails/plugins/legacy/).

They got legacified then, instead.

So, I guess (i.e. what I did was…) you need to svn remove the old plugin, and then re-install it. This time, don’t use piston or svn:externals as I doubt those plugins are ever going to change again.

ruby script/plugin install http://svn.rubyonrails.org/rails/plugins/legacy/simply_helpful

And life moves on again.

Related posts:

  1. Closing in on The Dream: “one-click-to-deploy Rails apps” Got a simple app you want to build? Allocate...
  2. Need Rails Developers? Hire Australians There’s been some malarky very recently about “how do...
  3. Rails 2.0 TextMate bundle – Tasty Tidbit – respond_to and view navigation The new release of the Rails TextMate bundle is coming...
  4. One-stop JavaScript Unit Testing for Rails 2.0 Previously, I mentioned a multi-step/multi-project solution to doing JavaScript Unit...
  5. Get ready for the TextMate “Trundle to Rails 2.0 Bundle” Have you noticed lately that the Rails TextMate git...
Trackbacks

Use this link to trackback from your own site.

Comments

Leave a response

  1. Josh Wed, 11 Jul 2007 20:11:25 UTC

    All the other features scheduled to be removed by Rails 2.0 will most likely suffer the same fate. So if anyone wants to take charge of a legacy plugin, just copy it into your own subversion repo and take good care of it.

  2. Pat Maddox Wed, 11 Jul 2007 21:10:31 UTC

    I’ve found Piston to be an excellent tool to avoid problems like this.

  3. Josh Knowles Wed, 11 Jul 2007 22:37:11 UTC

    Not that it matters, but it was me who commented on your ticket pointing out the legacy directory. Too many Joshs!!!

  4. adzap Wed, 11 Jul 2007 23:13:44 UTC

    I think a ‘piston switch’ would have got the job done. Not on the web page but here is the blog http://blog.teksol.info/articles/2007/01/22/piston-1-3-0-switch-goodness

    But that’s a little besides the point.

  5. Josh Wed, 11 Jul 2007 23:26:52 UTC

    @Josh Knowles [via] –

    LOL, I agree.

  6. Brian Wed, 11 Jul 2007 23:46:17 UTC

    I am tired of this problem. Edge rails is that, the edge, not the main stream. I just downloaded the latest version of restful_authentication and all the test require edge because they use the assert_difference methods. Edge has a lot of cool features, but until it is out you should write your code and plugins to work with the current release.

    @Nic – The path you gave failed for me

  7. Dr Nic Thu, 12 Jul 2007 00:33:16 UTC

    @Josh Knowles [via] – aye whoops. Fixed.

    @Brian [via] – true, but there is no “1.2.3″ version of each plugin, only an “edge” set of plugins. The tag 1_2_3 doesn’t include the plugins. Perhaps future releases could include the plugins and spinoffs folders.

    @adzap [via] – ooh, thx for that. Indeed piston is great.

  8. Dr Nic Thu, 12 Jul 2007 00:39:31 UTC

    @Brian [via] – sorry – I used the browser url. I’ve updated the commands to use the svn url.

Comments