This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 113112 - Rails plugin manager - unknown command
Summary: Rails plugin manager - unknown command
Status: RESOLVED FIXED
Alias: None
Product: ruby
Classification: Unclassified
Component: Rails (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Erno Mononen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-17 17:46 UTC by Tomas Danek
Modified: 2008-02-07 21:06 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
screenshot (70.98 KB, image/png)
2007-08-17 17:47 UTC, Tomas Danek 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Danek 2007-08-17 17:46:37 UTC 
20070817
--------------
- create new rails project, use native ruby
- invoke Rails plugins
- Find New - add all repositories (67 in my case)
- go back to New plugins and and click Reload plugins - 

result is on screenshot (attached)
Comment 1 Tomas Danek 2007-08-17 17:47:57 UTC 
Created attachment 46801 [details]
screenshot
Comment 2 Tomas Danek 2007-10-02 17:08:57 UTC 
marking as fix in 6.0, since this may be expected scenario
Comment 3 Torbjorn Norbye 2007-10-16 00:28:07 UTC 
This seems to be a bug in the Rails plugin command itself. Once I've configured my Rails projects with all those extra
repositories, just running the plugin command on the command line produces the same output:

% jruby script/plugin list
Unknown command:
Usage: plugin [OPTIONS] command 
etc.
Comment 4 Erno Mononen 2008-01-18 16:15:20 UTC 
Could you please try with the latest build? Seems to work for me with the latest build / Ruby 1.8.6 / Rails 2.0.2.
Comment 5 Torbjorn Norbye 2008-01-18 16:19:41 UTC 
Yeah, when I switched from JRuby 1.0.2 to JRuby 1.0.3, that included a new version of RubyGems - perhaps that fixes this
bug?
Comment 6 Erno Mononen 2008-02-07 21:06:52 UTC 
Closing, please reopen if this still doesn't work for you on 1.0.3. Assuming that this was fixed by the update as per 
Tor's comment.