This project is archived and is in readonly mode.
Generator::Commands::Create#file git broken with app generator
Reported by keturn | February 8th, 2010 @ 05:43 AM | in 2.3.10
The git support for
Generator::Commands::Create#file
uses
relative_destination
. But when doing the initial app
generation, the working directory is the parent of the app
directory, and from there relative_destination
is
broken. This results in a pile of error messages like
$ rails fooproj --git
create Rakefile
fatal: pathspec 'Rakefile' did not match any files
...
create log/test.log
fatal: pathspec 'log/test.log' did not match any files
...not that you really want log/test.log tracked by your VCS, but that's another story.
Comments and changes to this ticket
-
keturn February 8th, 2010 @ 05:46 AM
this refers to the 2.3-stable branch. That code has been moved around in master and I haven't checked to see if this is applicable.
-
Mikel Lindsaar February 8th, 2010 @ 10:45 AM
- State changed from new to open
- Assigned user set to Mikel Lindsaar
- Milestone set to 2.3.6
I have checked on Rails 3.0 and this is not an issue. Changed milestone to 2.3.6, need to verify.
-
Rizwan Reza May 16th, 2010 @ 02:41 AM
- Tag changed from app, generator, git to app, bugmash, generator, git
-
AllenWei May 16th, 2010 @ 09:50 AM
@keturn is right,relative destination should be change to absolute destination. we create rails application in parent directory.
Another issue is, if user want to create rails application with git support, we need init git repository for the newly created rails application.
-
Jeremy Kemper August 30th, 2010 @ 02:28 AM
- Milestone changed from 2.3.9 to 2.3.10
- Importance changed from to Low
-
Santiago Pastorino February 2nd, 2011 @ 04:49 PM
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 February 2nd, 2011 @ 04:49 PM
- State changed from open to stale
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>