Good catch! It's here: https://issues.apache.org/jira/browse/LANG-363
and the svn update here http://svn.apache.org/viewvc/commons/proper/lang/trunk/src/java/org/apache/commons/lang/StringEscapeUtils.java?r1=560660&r2=588534 That's annoying. Our current test breaks with commons-lang trunk, but if we change Velocity test to have the new result, it will break with commons lang released. Guess we can just remove that line item in the test. WILL On 10/30/07, Nathan Bubna <[EMAIL PROTECTED]> wrote: > > On 10/30/07, Velocity Gump <dev@velocity.apache.org> wrote: > ... > > [junit] Running org.apache.velocity.test.BuiltInEventHandlerTestCase > > [junit] Caught invalid references (local configuration). > > [junit] Caught invalid references (global configuration). > > [junit] Correctly escaped HTML > > [junit] Correctly escaped XML > > [junit] Correctly escaped SQL > > [junit] Correctly escaped Javascript > > [junit] Escape matched all references (global configuration) > > [junit] Successfully engine init() > > [junit] Escaping test1: Jimmy's <b>pizza</b> > > [junit] Successfully escaped test1: > > [junit] Escaping test1_js: Jimmy\'s <b>pizza<\/b> > > [junit] expected:<......> but was:<...\...> > > [junit] junit.framework.ComparisonFailure: expected:<......> but > was:<...\...> > ... > > looks like commons-lang has changed something in their javascript > escaping? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com
