search

remarkable-rb / remarkable

Simplifying tests!
http://www.nomedojogo.com/category/remarkable/
MIT License
120 stars 64 forks source link

Add gemspecs #36

Open xxx opened 12 years ago

xxx commented 12 years ago

It would be great to be able to use remarkable with Rails 3.1 without deprecation warnings, but there's no way to do that right now without forking the gem, due to lack of gemspecs. Either adding gemspecs, or releasing a new version of the gem would resolve this.

[Edit by Hosh: Moved Rails 3.1 without deprecation to a different issue #32]

hosh commented 12 years ago

These are two separate issues. Someone has asked for gemspecs ... and now that I've worked with using git submodule without them, it's enough of an itch that I'll go ahead and do that.

Rails 3.1 without deprecation warning is in the works in the Rails 3.1 branch.

xxx commented 12 years ago

ack, yeah I'm using the 3.1 branch, but had to fork because I can't point a Gemfile at a repo that doesn't have gemspecs, or alternately use a released gem that includes the 3.1 fixes. Didn't intend the 3.1 deprecations to be part of this.

hosh commented 12 years ago

@xxx roger.

bitcoiners commented 12 years ago

any progress on the gemspecs?

dmathieu commented 12 years ago

Please, do this. All the rails warnings are getting boring.

ippy04 commented 12 years ago

+1

tigrish commented 12 years ago

I'm running into this issue too, trying to upgrade an app to rails 3.2.

sujoyg commented 12 years ago

The lack of a gemspec is preventing us from using this with Rails 3.2. The issues with primary_key_name seems to have been been fixed in master, but an updated gem not released yet. On the other hand, lack of a gemspec file makes it impossible to pull the latest code in the project Gemfile.

saks commented 12 years ago

Can anyone tell me, what is the problem with releasing new version ir adding gemspec?

xxx commented 12 years ago

I ended up forking the repo and adding gemspecs where we needed them. We're using it in 3.2 right now without issue.

tigrish commented 12 years ago

We couldn't wait for progress on this so we ended up migrating our app to shoulda_matchers which provides much of the same functionality.

Too bad, I really liked this project...

On 31 Mar 2012, at 21:39, Michael Dunganreply@reply.github.com wrote:

I ended up forking the repo and adding gemspecs where we needed them. We're using it in 3.2 right now without issue.

Reply to this email directly or view it on GitHub: https://github.com/remarkable/remarkable/issues/36#issuecomment-4861087

hosh commented 12 years ago

@tigrish shoulda_matchers may be a better fit for most people anyways. I'm not entirely satisfied with the backend but oh well.

hosh commented 12 years ago

@saks Time. I just recently signed up to Opscode so I'll have some free time coming up this week.