plugin installation rescues errors and leads to confusion

The railtie plugin command rescues errors and then reports a plugin not found issue when it is definitely not the case:

    rescue StandardError => e
      puts "Plugin not found: #{args.inspect}"
      puts e.inspect if $verbose
      exit 1
    end

For instance, you can replicate this by trying to install a fork of active_scaffold:

beet/as_test active_scaffold > script/rails plugin --verbose install git://github.com/vhochstein/active_scaffold.git
Plugins will be installed using http
git init
Initialized empty Git repository in /Users/jack/git/beet/as_test/vendor/plugins/active_scaffold/.git/
git pull --depth 1 git://github.com/vhochstein/active_scaffold.git
remote: Counting objects: 320, done.
remote: Compressing objects: 100% (288/288), done.
remote: Total 320 (delta 29), reused 195 (delta 12)
Receiving objects: 100% (320/320), 202.92 KiB, done.
Resolving deltas: 100% (29/29), done.
From git://github.com/vhochstein/active_scaffold
 * branch            HEAD       -> FETCH_HEAD
removing: .git .gitignore
Plugin not found: ["git://github.com/vhochstein/active_scaffold.git"]
#<NameError: uninitialized constant ActiveScaffold>

Only with --verbose do you see it's actually a NameError from inside the plugin. Without it people will get confused as it looks like the plugin is there, and yet "Plugin not found".

I'm opening this to create a discussion on what would be a better solution. Should be easy enough to patch (happy to write it myself) when we agree on a better way of handling this.

I would imagine a more specific rescue would work well here. I'm going to try and replicate how a plugin could be installed but actually not found. In the meantime, any other thoughts?

Edited by Rohit Arondekar for formating.