Question

在Rails 2.3.11项目中我只有gem“aws-s3”（v：0.6.2）正常工作，但是因为我添加了（对于依赖项）gem“aws”（v：2.5.6）我在杂种启动期间发现了一些警告：

/Users/me/.rvm/gems/ree-1.8.7-2011.03/gems/aws-2.5.6/lib/ses/../awsbase/utils.rb:105: warning: already initialized constant HEX
/Users/me/.rvm/gems/ree-1.8.7-2011.03/gems/aws-2.5.6/lib/ses/../awsbase/utils.rb:107: warning: already initialized constant TO_REMEMBER
/Users/me/.rvm/gems/ree-1.8.7-2011.03/gems/aws-2.5.6/lib/ses/../awsbase/utils.rb:108: warning: already initialized constant ASCII
/Users/me/.rvm/gems/ree-1.8.7-2011.03/gems/aws-2.5.6/lib/ses/../awsbase/errors.rb:128: warning: already initialized constant DEFAULT_CLOSE_ON_4XX_PROBABILITY
/Users/me/.rvm/gems/ree-1.8.7-2011.03/gems/aws-2.5.6/lib/ses/../awsbase/parsers.rb:47: warning: already initialized constant DEFAULT_XML_LIBRARY
/Users/me/.rvm/gems/ree-1.8.7-2011.03/gems/aws-2.5.6/lib/ses/../awsbase/awsbase.rb:66: warning: already initialized constant AMAZON_PROBLEMS
/Users/me/.rvm/gems/ree-1.8.7-2011.03/gems/aws-2.5.6/lib/ses/../awsbase/awsbase.rb:86: warning: already initialized constant DEFAULT_SIGNATURE_VERSION
/Users/me/Documents/development/prj/myprj/config/initializers/omniauth.rb:2: warning: already initialized constant VERIFY_PEER

但该应用程序运行良好。你认为会有一些陷阱吗？关于如何解决此警告的任何建议？

非常感谢！

Answer 1

我不知道这些宝石之间是否存在任何不兼容性，所以你应该没问题。另外，在生产中运行时是否看到了这些警告（即：cache_classes = true）？这可能只是由于Rails开发中的重新加载。

Answer 2

我不认为同时放这两种方法是更好的方法此aws-s3宝石是适用于Ruby的AWS开发工具包的一部分。因此，冷杉从您的项目中都删除了并使用aws-sdk的s3模块创建一个干净的项目，使用aws-sdk的内部s3函数

宝石“aws”和“aws-s3”之间的冲突？

2 个答案: