It was never inteded to. Having it bundled in was an oversight.
marcel
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).
marcel
