You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@buildr.apache.org by "Peter Donald (JIRA)" <ji...@apache.org> on 2011/06/22 12:11:24 UTC

[jira] [Closed] (BUILDR-529) Stop using the gem name "foo" in tests as that is the name of an actual gem

     [ https://issues.apache.org/jira/browse/BUILDR-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Donald closed BUILDR-529.
-------------------------------


> Stop using the gem name "foo" in tests as that is the name of an actual gem
> ---------------------------------------------------------------------------
>
>                 Key: BUILDR-529
>                 URL: https://issues.apache.org/jira/browse/BUILDR-529
>             Project: Buildr
>          Issue Type: Bug
>    Affects Versions: 1.4.2
>            Reporter: Peter Donald
>             Fix For: 1.4.3
>
>         Attachments: PrefixGemNameWithBuildr.diff
>
>
> So there seems to be a gem named foo (See [1]). Buildr currently uses this as a gem name during testing. 
> Whilst attempting to track down a CI failure (See [2])  it turns out that during the build process buildr is downloading and installing this gem (at least on WIndows 7). The attached patch renames the fake gem from foo to buildr-foo to try and avoid this in the future.
> [1] https://rubygems.org/gems/foo
> [2] https://hudson.apache.org/hudson/job/Buildr-ci-build-jruby-win32/lastCompletedBuild/testReport/(root)/Buildr__Application%20load_gems/should_default_to___0_version_requirement_if_not_specified/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira