Activesupport dependency conflict in new extension

[CameronCarroll]

Hi. I'm working on creating a new extension, but just ran headfirst into a dependency issue that I can't seem to resolve.

Using Spree 1.0.0.RC1, Ruby 1.9.2 (also tried 1.9.3), Rails 3.1.3 I'm creating a new Spree extension using 'Spree extension [foo]' Trying to do a bundle install fails due to an Activesupport dependency conflict:

In Gemfile:
spree_nexus3 (>= 0) ruby depends on
activesupport (~> 3.1.0) ruby
spree_nexus3 (>= 0) ruby depends on
activesupport (3.2.0.rc1)

Note that this is a completely raw extension with nothing in the gemfile or gemspec other than what was generated.

Thanks a lot,

Cameron

[radar]

Where is spree_nexus3 coming from?

[CameronCarroll]

Sorry, that's just my test extension name; Following the directions at http://edgeguides.spreecommerce.com/creating_extensions.html results in the dependency conflict.

I went ahead and tried creating an integrated extension just to see if that would change anything, but I still get the same conflict.

Thanks a lot,

Cameron

[schof]

I wasn't able to verify this. I created a new extension as follows

spree extension foofah
cd foofah
bundle install

I had the problem of a missing gemspec (due to a bug in RC1 which has since been fixed) but once I dropped this line from the Gemfile I did not have an issue.

I'll keep investigating. Next thing to try is to install Rails 3.2.0.rc1 in my gemset and see if that results in a problem.

[schof]

Unable to reproduce this in a standalone extension (even with Rails 3.2.0.rc1 installed locally.) Closing this out. We can always reopen if someone can provide steps to reproduce.