search

google-code-export / wro4j

Automatically exported from code.google.com/p/wro4j
1 stars 1 forks source link

Upgrade to Rhino 1.7R4 #674

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
You're going to need to upgrade to Rhino 1.7R4 in order to run JSHint 1.0.0 
because it triggers this bug: https://github.com/mozilla/rhino/issues/56

Also, now is a good time to let you know JSHint 1.0.0 is out :)

Original issue reported on code.google.com by cow...@bbs.darktech.org on 9 Feb 2013 at 3:01

GoogleCodeExporter commented 9 years ago 
Dang. It seems that upgrading Rhino is causing cssLint to hang. I'm going to 
need your help debugging this...

Original comment by cow...@bbs.darktech.org on 9 Feb 2013 at 3:09

GoogleCodeExporter commented 9 years ago 
Looks like we're in trouble: https://github.com/mozilla/rhino/issues/107

Original comment by cow...@bbs.darktech.org on 9 Feb 2013 at 3:21

GoogleCodeExporter commented 9 years ago 
Rhino 1.7R4 has serious bugs and there seems to be no progress on new release.

Original comment by alex.obj...@gmail.com on 9 Feb 2013 at 4:02

GoogleCodeExporter commented 9 years ago 
What's the alternative? Did you try http://openjdk.java.net/projects/nashorn/ 
yet?

Original comment by cow...@bbs.darktech.org on 9 Feb 2013 at 4:18

GoogleCodeExporter commented 9 years ago 
I filed https://github.com/jshint/jshint/issues/853 just in case.

Original comment by cow...@bbs.darktech.org on 9 Feb 2013 at 4:22

GoogleCodeExporter commented 9 years ago 
https://bitbucket.org/ramonza/nashorn-backport contains a backport of Nashorn 
for JDK7. http://java.dzone.com/articles/project-nashorn-javascripts claims 
that switching from Rhino to Nashorn is supposed to be relatively painless.

Original comment by cow...@bbs.darktech.org on 9 Feb 2013 at 4:29

GoogleCodeExporter commented 9 years ago 
using nashorn is on the roadmap. Another option is to use node.js.

Original comment by alex.obj...@gmail.com on 9 Feb 2013 at 4:44

GoogleCodeExporter commented 9 years ago 
Closing this issue with WONTFIX resolution, since rhino-1.7R4 has some critical 
bugs which make it unusable.

Original comment by alex.obj...@gmail.com on 10 Feb 2013 at 5:40

GoogleCodeExporter commented 9 years ago 
NOTE: According to https://github.com/mozilla/rhino/issues/107 this issue has 
been fixed in git master.

Original comment by cow...@bbs.darktech.org on 16 Feb 2013 at 5:38

GoogleCodeExporter commented 9 years ago 
Rhino 1.7R7 fixes the outstanding problem with csslint. It should be safe to 
upgrade now. Continuing this discussion in issue 490.

Original comment by cow...@bbs.darktech.org on 11 Mar 2013 at 4:17