You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Antoine Toulme (JIRA)" <ji...@apache.org> on 2010/04/10 19:48:41 UTC

[jira] Commented: (BUILDR-403) Buildr::Util::Gems.install does not find gems on remote sources

    [ https://issues.apache.org/jira/browse/BUILDR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855614#action_12855614 ] 

Antoine Toulme commented on BUILDR-403:
---------------------------------------

Pepjin, I tried to apply your patch but it doesn't work for me. It fails when trying to get to see what to install and what is not found. In my case it never finds the gem.

I find it a bit risky to call the gems index for real - on different platforms, different situations, this stuff might break. Can you try stubbing the code to avoid calling it ?

> Buildr::Util::Gems.install does not find gems on remote sources
> ---------------------------------------------------------------
>
>                 Key: BUILDR-403
>                 URL: https://issues.apache.org/jira/browse/BUILDR-403
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.3.5
>         Environment: Windows XP, JRuby 1.4.0, rubygems 1.3.6; not verified on other combinations
>            Reporter: Pepijn Van Eeckhoudt
>             Fix For: 1.4
>
>         Attachments: find_gem_specs.patch
>
>
> The gem installation code does not seem to be able to find gems on remote servers. The attached patch extracts the gem location code from install into a separate method and introduces two specs for this new method.
> On my configuration the 'locate remote gem' spec fails with the current trunk. Replacing the first statement of find_gem_specs with
> remote = dependencies.map{ |dep| Gem.source_index.search(dep).last || Gem::SpecFetcher.fetcher.fetch( dep, true ).map{ |spec, source| spec }.last }
> resolves the issue.
> This statement was distilled from the rubygems source code itself (see query_command). Discussions on mailing lists online seems to recommend the SpecFetcher class over the SourceInfoCache class (http://www.mail-archive.com/rubygems-developers@rubyforge.org/msg02087.html).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira