Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Fix resolving of Rails constant so it plays nice with Guard::Rails #17

Merged
merged 2 commits into from Nov 19, 2011

Conversation

Projects
None yet
2 participants
Contributor

johnbintz commented Nov 18, 2011

Was running guard-rails-assets in the same group as guard-rails and guard-rails-assets was not getting the right Rails constant. This fix ensures the right Rails constant is located for use.

Also, fixed an unrelated failing test.

dnagir added a commit that referenced this pull request Nov 19, 2011

Merge pull request #17 from johnbintz/master
Fix resolving of Rails constant so it plays nice with Guard::Rails

@dnagir dnagir merged commit 814bf00 into dnagir:master Nov 19, 2011

Owner

dnagir commented Nov 19, 2011

Thanks. I've released the gem so you can update.

I would definitely advise against running 2 Rails apps/instances. It is not something that is supported by any gem.
And earlier or later you'll probably face bigger issues.

I would rather create 2 guard groups and run them as separate processes.

Contributor

johnbintz commented Nov 19, 2011

Yeah that was just an accidental Guard run result when I was making a Guardfile. I know better, but still, it was a bug and BUGS MUST BE SQUASHED! stomps about

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment