Forums

We are investigating updating the compressor to work with Rhino 1.7 (and beyond for ES5 support), but that shouldn't matter for you unless you are trying to compress code that is using the latest JavaScript features (which shouldn't be the case if you are building a standard web application).

Invoke the compressor in its own process. It contains the version of Rhino it needs. Keep compressor out of the classpath for the rest of your deployment system.

I was wondering if there has been any progress in the area of Rhino 1.7.x support for in-application compression. I would be willing to donate time to the project if there is a forum (if this isn't it) to ask questions.

Thanks