jasmine deprecated?

[Rajan Agaskar]

So ...

Is it time to kill deprecated methods in jasmine yet? Since the
jasmine global var is deprecated, i get warnings in RubyMine. The rec
is to use Jasmine.getEnv instead, but Jasmine is somehow appearing as
deprecated (probably bad RubyMine inspections), so there's no joy
there either.

[Christian Williams]

the jasmine global var is deprecated?  i thought Jasmine (upper case) was deprecated.  [and i'm down for removing it, along with all the other @deprecateds, yeah].

--X [typos courtesy of my iPhone]

[Rajan Agaskar]

Hmm, some of this may be rubymine trying to be too smart.

So in base.js:

/** @deprecated use jasmine (lowercase because it's a package name) instead */
var Jasmine = jasmine;

In jasmine.js (which arguably, should be killed, right? If we want a one-stop jasmine.js, we should have a minified version that's built on a post-commit or rake task or something):

/** @deprecated use Jasmine.getEnv() instead */
var jasmine = Jasmine.currentEnv_;

This would explain why both Jasmine and jasmine show up deprecated. Killing jasmine.js would be a happy solution to my problems and probably make more sense to our users, but it might mean someone's got to undertake the building jasmine.js rake/shell script task.

[Davis Frank]

Carl and I have a lot of stuff to do in this regard in the next week.  I'll have some questions about Jasmine when we finish up gem-ifying Pockets, which should happen by EOD Tuesday.

Let's plan to talk about Jasmine a bit after the Jasmine talk on Wed.  I assume you guys will all be there to represent...

--dwf