Running script/plugin install
svn://rubyforge.org/var/svn/laszlo-plugin/tags/openlaszlo fails,
returning the help information for the “export” command:
export: Create an unversioned copy of a tree.
usage: 1. export [-r REV] URL [PATH]
2. export [-r REV] PATH1 [PATH2]
etc…
Has anyone encountered this before?
System info:
Mac OS 10.4.4.
ruby 1.8.2 (2004-12-25)
svn, version 1.1.3 (r12730)
rails 1.0.0
I suspect that the syntax of the svn export command has subtely
changed, or is at least different with your version of SVN than that
expected by the script/plugin command. You might get it working
fastest by downgrading your version of SVN.
On 2/5/06, Nick C. [email protected] wrote:
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails
–
James A. wrote:
I suspect that the syntax of the svn export command has subtely
changed, or is at least different with your version of SVN than that
expected by the script/plugin command. You might get it working
fastest by downgrading your version of SVN.
Thanks for the reply James - I’ve tried downgrading through 1.3 to
1.1.3, with no joy so far, but might keep going just in case.
Also, I have just noticed that script/plugin install
svn://rubyforge.org/var/svn/laszlo-plugin/tags/openlaszlo works fine
when run via Locomotive. Perhaps Locomotive comes with an earlier
version of svn? Does anyone know which version, or how I could find out?
I wish I knew.
I’ve been trying to hack at the same problem for over 3 hours,
re-installing svn, etc., etc. There are a number of people who are
experiencing problems with this, but there doesn’t seem to be any
adequate response. The issue would appear to be with how the plugin
architecture handles the svn calls, but I have no idea really. I spent
a good two hours scouring the wiki, google, mailing lists, etc.
The best I can tell you is to just use svn directly and check out a
copy of the plugin into the correct folder (which is essentially what
“plugin” is supposed to do for you). Like so:
$ cd vendor/plugins
$ svn co
That’ll do the trick for now.
David Andrew T.
http://dathompson.blogspot.comRunning script/plugin install
svn://rubyforge.org/var/svn/laszlo-plugin/tags/openlaszlo fails,
returning the help information for the “export” command:export: Create an unversioned copy of a tree.
usage: 1. export [-r REV] URL [PATH]
2. export [-r REV] PATH1 [PATH2]
etc…
Update - this appears to be a general error with script/plugin install,
and is not specific to the openlaszlo plugin. I’ve tried installing the
engines plugin and the result is the same. My Locomotive installation
will happily install plugins via script/plugin install, and I’ve
verified that the version of svn is the same.
Would anyone be kind enough to offer suggestions as to what might be
causing this behaviour?
David Andrew T. wrote:
I’ve been trying to hack at the same problem for over 3 hours,
re-installing svn, etc., etc.
Me too David - it’s reassuring to see that there are others in
the same boat. Like you suggest, I’ve been using:
$ cd vendor/plugins
$ svn export
but am looking for a more permanent fix. The fact that Locomotive
uses the same version of svn that I’ve built and works flawlessly
makes me think it’s something more than just the version number
that’s at fault. If anyone reading has any more suggestions there
are a few of us who’d appreciate the hints!
+1
Who maintains the plugin stuff? Does it require svn? Anyone?
b
I’ve been using the RadRails eclipse plugin for my rails development
IDE. Their rails plugin wizard seems to work fine, but I’m not sure
what version of SVN they are using.
It would great to find out how to bring this to the right people’s
attention.
Dave
On 2/6/06, n1c [email protected] wrote:
but am looking for a more permanent fix. The fact that Locomotive
http://lists.rubyonrails.org/mailman/listinfo/rails
–
David Andrew T.
http://dathompson.blogspot.comThanks for the tip… I’d tried running the plugin script on the command
line. I got stuck with it apparently wanting
svn to be installed and I put it off until sometime when I’d get around
to installing subversion… forgot that radrails
has svn built in… it does right?
…
Hmm, wait a minute… are you talking about the Generators view? I see
that that has “plugin” as an option but it looks
like it runs “script/generate plugin”, not “script/plugin …”. Have you
found some way to /install/ plugins in radrails?
thanks,
b
For Radrails, I’m using 0.5.3. In the Generators menu, the pulldown
menu should have plugin as an option at the very end of the list. Then
you can run any command that you normally would from the command line
in the text field to the right.
Seriously…Radrails is making some serious headway!
Dave
On 2/6/06, Ben M. [email protected] wrote:
Dave
David Andrew T.
–
David Andrew T.
http://dathompson.blogspot.comHmmm…actually after looking this over it would appear that this is
not actually running the plugin script, but is generating the tree for
the creation of a new plugin. Sorry for the confusion.
It would appear that using SVN directly is the only option at this
point. 
Dave
On 2/6/06, David Andrew T. [email protected] wrote:
Thanks for the tip… I’d tried running the plugin script on the command line. I got stuck with it apparently wanting
b$ cd vendor/plugins
–
David Andrew T. http://dathompson.blogspot.com
–
David Andrew T.
http://dathompson.blogspot.comWhoops… I hit send and then saw your reply… yeah, I guess I’ll just
have to install subversion.
b
It looks like someone already submitted this as a problem. See
http://dev.rubyonrails.org/ticket/2795. I changed my directory to one
without spaces and plugins worked
David Andrew T. wrote:
For Radrails, I’m using 0.5.3. In the Generators menu, the pulldown
menu should have plugin as an option at the very end of the list.
Then
you can run any command that you normally would from the command line
in the text field to the right.
Yes, but if I do that it runs “script/generate plugin ”.
So, if I try to run “script/plugin discover”, it
runs “script/generate plugin discover” instead and generates a
“discover” plugin stub under vendor… not really what I
was looking for.
It doesn’t look like there’s any way to use radrails to install plugins
into a project… Well, actually, once I have
the radrails terminal open (it seems overly difficult to get a terminal
open), I can type “script/plugin list” in the
terminal. But that seems to have the same problem as running it from the
command line:
test> ruby script\plugin list
-e: No such file or directory - svn ls
http://dev.rubyonrails.com/svn/rails/plugins/
c:/ruby/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/commands/plugin.rb:313:in
plugins': private method split’ called for
nil:NilClass (NoMethodError)
from
c:/ruby/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/commands/plugin.rb:469:in
parse!' from c:/ruby/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/commands/plugin.rb:469:in map’
from
c:/ruby/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/commands/plugin.rb:469:in
parse!' from c:/ruby/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/commands/plugin.rb:411:in parse!’
test> from
c:/ruby/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/commands/plugin.rb:427:in
parse!' from c:/ruby/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/commands/plugin.rb:823 from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:18:in require__’
from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:18:in
require' from c:/ruby/lib/ruby/gems/1.8/gems/activesupport-1.2.5/lib/active_support/dependencies.rb:214:in require’
from ./script\plugin:3
from -e:3:in `load’
from -e:3
Still no plugins for me! :-/
b
Dominic,
Excellent! That seems to have done the trick for me. I’m going to try
and update the wiki’s tonight with the note.
The link to the ticket doesn’t seem to reference the ticket you were
speaking of (unless I’m just clueless). What was the ticket number?
Also, I can’t seem to figure out how to search tickets using keywords.
Am I missing something?
Dave
On 2/6/06, Dominic S. [email protected] wrote:
plugin discover" instead and generates a “discover” plugin stub under
Peak Obsession
c:/ruby/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/commands/plugin.rb:469:in`require’
…
Me too David - it’s reassuring to see that there are others in
–
Rails mailing list
–
David Andrew T.
http://dathompson.blogspot.comDominic S. <dsisnero@…> writes:
It looks like someone already submitted this as a problem. See
http://dev.rubyonrails.org/ticket/2795. I changed my directory
to one without spaces and plugins worked
Fantastic - thanks very much for this info Dominic - this has
solved it for me as well. The directory I was working from is a
subdirectory of the OpenLaszlo server, which by default
installs to a path containing the folder “OpenLaszlo Server 3.1.1”.
Removing the spaces has fixed the problem, and also explains why
Locomotive works - it doesn’t allow spaces in the path to the project
file at all - very sensible!
I see a note has now been added to the rails wiki here:
http://wiki.rubyonrails.com/rails/pages/Plugins
I’m using svn v1.3.0 on Mac OSX Tiger (built w/ darwin ports) and
script/plugin works fine.
I’m really curious why this isn’t working. script/plugin has a
verbose mode, but unfortunately it does not output the svn command.
I’ve added a patch to add this: http://dev.rubyonrails.org/ticket/3755
script/plugin -v install foo -o # checkouts out the foo plugin
Here’s how it constructs the svn command too, if it might help anyone:
base_cmd = “svn #{cmd} #{uri} "#{root}/vendor/plugins/#{name}"”
base_cmd += ’ -q’ if options[:quiet] and not $verbose
base_cmd += " -r #{options[:revision]}" if options[:revision]
–
Rick O.
http://techno-weenie.net
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs