This project is archived and is in readonly mode.
script/plugin install fails doesn't populate new directory in vendor/plugins
-
Josh Nichols
- Tag changed from 2.3.4, git, install, scriptplugin to 2.3.4, bugmash, git, install, scriptplugin
-
Rizwan Reza
I can't seem to reproduce this error. The plugin is cloned into the plugins directory as it should.
-
Rizwan Reza
I used Git version 1.6.5.2.
-
Jeremy Kemper
- State changed from new to resolved
-
Josh Nichols
I've tested with a non-RC version, 1.6.6, and still see the same behavior.
Looking at the code suggests that something about the git command is not exiting cleanly (ie non-zero exit code), and falling into the else clause that silently removes the failed-to-clone plugin.
-
Rizwan Reza
- Tag changed from 2.3.4, bugmash, git, install, scriptplugin to 2.3.4, git, install, scriptplugin
-
masone
- Importance changed from to
Can't reproduce this either. The return code from git is 0.
OSX, git version 1.6.5.1, ruby 1.8.7 (2010-06-23 patchlevel 299)
Josh: It does a
pull --depth 1because this only fetches the newest revision. A clone would get the whole history too. -
Santiago Pastorino
- Tag changed from 2.3.4, git, install, scriptplugin to 234, git, install, scriptplugin
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
Santiago Pastorino
- State changed from open to stale