ActiveResource will not ship with Rails 1.2

[Channer Teomond]

http://dev.rubyonrails.org/changeset/5554

--
Posted via http://www.ruby-forum.com/.

[Roderick van Domburg]

Indeed, that grabbed my attention as well.

It's great that 1.2 will support the "publishing" REST interfaces right
out of the box. At the same time, not having the functionality to
consume them does make it feel a bit half-done and may defer the Coming
of a New Web Service Age.

Here's to hoping a plugin for 1.2 will be stubbed out of Edge Rails!

[Marcel Molina Jr.]

On Mon, Nov 20, 2006 at 08:21:24PM +0100, Channer Teomond wrote:
> http://dev.rubyonrails.org/changeset/5554

It was never inteded to. Having it bundled in was an oversight.

marcel
--
Marcel Molina Jr. <mar...@vernix.org>

[Channer Teomond]

Roderick van Domburg wrote:
> Indeed, that grabbed my attention as well.
>

Well on the positive side RJS wasn't done either when Rails 1.0 was
released but they shipped it soon after and it was fully baked by then.
I'm sure we'll see the rest of REST (no pun intended) ship soon after.
I think they just want to get 1.2 out the door. Probably on the Dec.
anniversary of launching 1.0.

From the notes in SVN it looks like the release candidate is coming.

I do wonder how many books going to press are going to get screwed up
though refering to the 1.2 REST support in Rails?

[Roderick van Domburg]

Marcel Molina Jr. wrote:
> It was never inteded to. Having it bundled in was an oversight.

Could you tell us more about the release scheduling of ActiveResource
(or the Rails version it'll be included in, for that matter)?

- Roderick

[Marcel Molina Jr.]

On Mon, Nov 20, 2006 at 09:37:00PM +0100, Roderick van Domburg wrote:
> Marcel Molina Jr. wrote:
> > It was never inteded to. Having it bundled in was an oversight.
>
> Could you tell us more about the release scheduling of ActiveResource
> (or the Rails version it'll be included in, for that matter)?

All "included in Rails" would mean is that it is marked as a dependency in
the gem specification so that when you do "sudo gem install rails" it would
slurp down ActiveResource.

If we never bundled ActiveResource with rails, all you'd ever have to do if
you were planning on using it in a rails app is "sudo gem install
activeresource".

As for when ActiveResource will be released as a gem, regardless of whether
rails will mark it as a dependency, there is currently no set timeline.

We are currently using it already in production at 37signals and so are at
least a couple other people in core (or at least, it appears they will be
soon).