RM 3.1 ignores local gem paths in Gemfile?

Just started to try RM 3.1...

I am actively developing and maintaining a few Rails 3 engines and plugins (irt, hobo, dryml, hobo_fields, hobo_support, etc...), and I usually link the gems in the Gemfile with:

gem "foo", :path => "/path/to/foo"

so I can change the gem and try it in a rails app without building and installing the gem (which would be a real pain!).

I don't find any way to attach the local gems to the app. Am I missing something or has it just been forgotten during the implementation?

Is there any work around in order to attach some local file, lib dir, or gem somehow so I could extend the "smartness" of RM to that gems?
Is there any possibility to edit/add some path to the "External Libraries" node in the Project pane?

4 comments
Comment actions Permalink

I have just found an interesting thing that seems related to the problem: for each gem statement that uses a local path in the Gemfile, there is an error in the server console at launch:

sh: git: command not found

That makes me think that probably RM or some other code tries to look for a git repo, but the git command is not available in that environment. That's sort of weird because `which git` returns the correct path. Any idea about that error?

0
Comment actions Permalink

Just an update: http://devnet.jetbrains.net/docs/DOC-1160 fixed the sh: git error, but the local gems are still ignored

0
Comment actions Permalink

Domizio, thank you for creating an issue http://youtrack.jetbrains.net/issue/RUBY-8105, I'll take a look at this problem

0
Comment actions Permalink

Dennis, thank you for fixing it! ;-)

0

Please sign in to leave a comment.