Dropping JsonML support in the Closure Compiler

[John Lenz]

The Closure Compiler team was interested in dropping JsonML support from the Closure Compiler but it appears that Caja has a dependency on it:

  https://code.google.com/p/google-caja/source/browse/trunk/src/com/google/caja/parser/js/JsonMLCompatible.java?r=5606&spec=svn5660

Is this a feature people are actually using with Caja? (We were under the impression it was not).

[Kevin Reid]

I'm not familiar with the history of this feature, so if someone knows I've missed something, please speak up.

As far as I can tell from a few searches of our code, this interface is implemented but not used.

Furthermore, with the deprecation of ES5/3 and the cajoler, our Java components are not intended for external use (they remain only for build/test), so no one should be using them and we ought to remove them entirely.

[Kevin Reid]

On Mon, Feb 24, 2014 at 9:42 AM, Kevin Reid <kpr...@google.com> wrote:

As far as I can tell from a few searches of our code, this interface is implemented but not used.

Furthermore, with the deprecation of ES5/3 and the cajoler, our Java components are not intended for external use (they remain only for build/test), so no one should be using them and we ought to remove them entirely.

Done. As of r5669 there are no more references to JsonML in Caja. (Well, one include rule I missed in the build, but that will do no harm.)