You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Pepijn Van Eeckhoudt (JIRA)" <ji...@apache.org> on 2010/03/17 10:02:27 UTC
[jira] Created: (BUILDR-403) Buildr::Util::Gems.install does not
find gems on remote sources
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
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.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (BUILDR-403) Buildr::Util::Gems.install does not
find gems on remote sources
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme resolved BUILDR-403.
-----------------------------------
Resolution: Fixed
I introduced the main code change you wanted to make and changed the specs to match the new API.
Please try it out: if you still want to put the method aside to have specs on it specifically we can do that for sure.
15:29:03~/w/buildr>svn ci CHANGELOG lib/buildr/core/util.rb spec/core/application_spec.rb -m "BUILDR-403: Buildr::Util::Gems.install does not find gems on remote sources"
Sending CHANGELOG
Sending lib/buildr/core/util.rb
Sending spec/core/application_spec.rb
Transmitting file data ...
Committed revision 998357.
> 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
> Assignee: Antoine Toulme
> Fix For: 1.4.2
>
> Attachments: find_gem_specs.patch, find_gem_specs2.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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-403) Buildr::Util::Gems.install does not
find gems on remote sources
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910921#action_12910921 ]
Hudson commented on BUILDR-403:
-------------------------------
Integrated in Buildr-ci-build #121 (See [https://hudson.apache.org/hudson/job/Buildr-ci-build/121/])
> 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
> Assignee: Antoine Toulme
> Fix For: 1.4.2
>
> Attachments: find_gem_specs.patch, find_gem_specs2.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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (BUILDR-403) Buildr::Util::Gems.install does not
find gems on remote sources
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme updated BUILDR-403:
----------------------------------
Fix Version/s: 1.4.2
(was: 1.4.1)
> 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.2
>
> Attachments: find_gem_specs.patch, find_gem_specs2.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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-403) Buildr::Util::Gems.install does not
find gems on remote sources
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910816#action_12910816 ]
Antoine Toulme commented on BUILDR-403:
---------------------------------------
Pepijn, this patch breaks specs for application_spec.rb.
I'm going to try to integrate the change you describe in the description of the bug though.
> 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.2
>
> Attachments: find_gem_specs.patch, find_gem_specs2.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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-403) Buildr::Util::Gems.install does not
find gems on remote sources
Posted by "Pepijn Van Eeckhoudt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856002#action_12856002 ]
Pepijn Van Eeckhoudt commented on BUILDR-403:
---------------------------------------------
Patch attached. The patch is for the code as it currently exists in SVN; not for when the first patch is applied.
> 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.1
>
> Attachments: find_gem_specs.patch, find_gem_specs2.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
[jira] Updated: (BUILDR-403) Buildr::Util::Gems.install does not
find gems on remote sources
Posted by "Pepijn Van Eeckhoudt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pepijn Van Eeckhoudt updated BUILDR-403:
----------------------------------------
Attachment: find_gem_specs2.patch
Reuploaded the patch, granting license for inclusion this time.
> 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.2
>
> Attachments: find_gem_specs.patch, find_gem_specs2.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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-403) Buildr::Util::Gems.install does not
find gems on remote sources
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (BUILDR-403) Buildr::Util::Gems.install does not
find gems on remote sources
Posted by "Pepijn Van Eeckhoudt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855863#action_12855863 ]
Pepijn Van Eeckhoudt commented on BUILDR-403:
---------------------------------------------
Antoine,
The patch attached to this issue is supposed to fail. The only change is that I extracted the current code as is to a method so I could write a unit test for that method. Otherwise I had no easy way of demonstrating the current issue.
The actual fix is described in the issue description. That change is essentially a modification of the 'find gem' logic so that it reflects the way the gem query command does its gem search.
> 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.1
>
> 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
[jira] Updated: (BUILDR-403) Buildr::Util::Gems.install does not
find gems on remote sources
Posted by "Pepijn Van Eeckhoudt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pepijn Van Eeckhoudt updated BUILDR-403:
----------------------------------------
Attachment: (was: find_gem_specs2.patch)
> 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.2
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (BUILDR-403) Buildr::Util::Gems.install does not
find gems on remote sources
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme reassigned BUILDR-403:
-------------------------------------
Assignee: Antoine Toulme
> 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
> Assignee: Antoine Toulme
> Fix For: 1.4.2
>
> Attachments: find_gem_specs.patch, find_gem_specs2.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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-403) Buildr::Util::Gems.install does not
find gems on remote sources
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887135#action_12887135 ]
Antoine Toulme commented on BUILDR-403:
---------------------------------------
OK, the patch fails the specs, and doesn't have the little feather, so I cannot use 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.2
>
> Attachments: find_gem_specs.patch, find_gem_specs2.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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (BUILDR-403) Buildr::Util::Gems.install does not
find gems on remote sources
Posted by "Pepijn Van Eeckhoudt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pepijn Van Eeckhoudt updated BUILDR-403:
----------------------------------------
Attachment: find_gem_specs.patch
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (BUILDR-403) Buildr::Util::Gems.install does not
find gems on remote sources
Posted by "Pepijn Van Eeckhoudt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pepijn Van Eeckhoudt updated BUILDR-403:
----------------------------------------
Attachment: find_gem_specs2.patch
> 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.1
>
> Attachments: find_gem_specs.patch, find_gem_specs2.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
[jira] Commented: (BUILDR-403) Buildr::Util::Gems.install does not
find gems on remote sources
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855996#action_12855996 ]
Antoine Toulme commented on BUILDR-403:
---------------------------------------
Pepjin, if you'd attach the code in the description as another patch and check the checkbox to contribute the code to Apache, I'll be able to use 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.1
>
> 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
[jira] Updated: (BUILDR-403) Buildr::Util::Gems.install does not
find gems on remote sources
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme updated BUILDR-403:
----------------------------------
Fix Version/s: 1.4.1
(was: 1.4)
Moving to 1.4.1. We are out of time to release 1.4.
> 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.1
>
> 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